Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eb4b787c9486484cf1df1ef88bb9910d9f7cedda471ba8f24a0a08916f9e5841

Tx prefix hash: d6e7c76b4d9deb065125247fae31a6d57f59f591c96b9acbba112450a521ee67
Tx public key: e9ec34b1124b1d5d6dbcfb5a5042f485576e59c2d698abb60c30b2acbfc6a472
Timestamp: 1733471160 Timestamp [UCT]: 2024-12-06 07:46:00 Age [y:d:h:m:s]: 00:158:05:19:26
Block: 1169132 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112903 RingCT/type: yes/0
Extra: 01e9ec34b1124b1d5d6dbcfb5a5042f485576e59c2d698abb60c30b2acbfc6a472021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d16e9e05df0127010323981f3ed04c606ccd458e51bd51b844dbbab4cde5e7f4 0.600000000000 1654845 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": 1169142, "vin": [ { "gen": { "height": 1169132 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d16e9e05df0127010323981f3ed04c606ccd458e51bd51b844dbbab4cde5e7f4" } } ], "extra": [ 1, 233, 236, 52, 177, 18, 75, 29, 93, 109, 188, 251, 90, 80, 66, 244, 133, 87, 110, 89, 194, 214, 152, 171, 182, 12, 48, 178, 172, 191, 198, 164, 114, 2, 17, 0, 0, 0, 7, 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