Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 847360c5ecaa8ccd7f05849e916383874d8781662d241c2eb00cc2c5f60021ec

Tx prefix hash: af442b7caf39cbd8569f33fcddc2e9770788d637e953a3e210e4cafba2da91d5
Tx public key: 28812c2120790193733fe0c9f66d7359f2a0e8ca6de7871b00b9a9462af63949
Timestamp: 1693989534 Timestamp [UCT]: 2023-09-06 08:38:54 Age [y:d:h:m:s]: 01:144:17:15:00
Block: 842093 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 364531 RingCT/type: yes/0
Extra: 0128812c2120790193733fe0c9f66d7359f2a0e8ca6de7871b00b9a9462af63949021100000003faf35c9c000000000000000000

1 output(s) for total of 0.994938851000 dcy

stealth address amount amount idx
00: f29a5d5c5b64cf4b0f5f028e1e77ec4e255969880c95596cb2bfe1bf803d415d 0.994938851000 1295185 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 842103, "vin": [ { "gen": { "height": 842093 } } ], "vout": [ { "amount": 994938851, "target": { "key": "f29a5d5c5b64cf4b0f5f028e1e77ec4e255969880c95596cb2bfe1bf803d415d" } } ], "extra": [ 1, 40, 129, 44, 33, 32, 121, 1, 147, 115, 63, 224, 201, 246, 109, 115, 89, 242, 160, 232, 202, 109, 231, 135, 27, 0, 185, 169, 70, 42, 246, 57, 73, 2, 17, 0, 0, 0, 3, 250, 243, 92, 156, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8