Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9472b17c09515ab811e72852224038e9a06e7876f39c6704fa35513bfe5e457c

Tx prefix hash: cac19bfa9efb774a6ec7efb6379210b07418e69f99281be2b2d3616d354d40c9
Tx public key: f1bc6f05d12459c079c382291b9a169aa013bcefa7789e1a9525921b3c2c49f7
Timestamp: 1737016630 Timestamp [UCT]: 2025-01-16 08:37:10 Age [y:d:h:m:s]: 00:156:20:01:10
Block: 1198481 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111738 RingCT/type: yes/0
Extra: 01f1bc6f05d12459c079c382291b9a169aa013bcefa7789e1a9525921b3c2c49f7021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bd5522e7878370099eca7ad561118b98ec57a512d24aadcf4107430199d0e1a4 0.600000000000 1685106 of 15

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": 1198491, "vin": [ { "gen": { "height": 1198481 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bd5522e7878370099eca7ad561118b98ec57a512d24aadcf4107430199d0e1a4" } } ], "extra": [ 1, 241, 188, 111, 5, 209, 36, 89, 192, 121, 195, 130, 41, 27, 154, 22, 154, 160, 19, 188, 239, 167, 120, 158, 26, 149, 37, 146, 27, 60, 44, 73, 247, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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