Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9b0ea2217fc7881767425e1c0d56e34bc06699597fa04d97e243a0d07841a13d

Tx prefix hash: a4043369ba3d4349c77e328fa75c0debc9f1684ce1bf4c7e84faeea296ea5a03
Tx public key: 66c4f2872cb0fa8f332f081a2e7b1939e9743e27f91e03b59b4741d18ad6490b
Timestamp: 1715843918 Timestamp [UCT]: 2024-05-16 07:18:38 Age [y:d:h:m:s]: 00:162:05:03:33
Block: 1023107 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 116146 RingCT/type: yes/0
Extra: 0166c4f2872cb0fa8f332f081a2e7b1939e9743e27f91e03b59b4741d18ad6490b02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cd0ed97a4e23549d34f690b7032b929f582a15b1e41bcef4caad11e268fa2390 0.600000000000 1487898 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": 1023117, "vin": [ { "gen": { "height": 1023107 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cd0ed97a4e23549d34f690b7032b929f582a15b1e41bcef4caad11e268fa2390" } } ], "extra": [ 1, 102, 196, 242, 135, 44, 176, 250, 143, 51, 47, 8, 26, 46, 123, 25, 57, 233, 116, 62, 39, 249, 30, 3, 181, 155, 71, 65, 209, 138, 214, 73, 11, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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