Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ff44732ca13977734bc7499604f77fad7a72e62e5ca147c43483da4a8eb28d7b

Tx prefix hash: 09f0d1a2c48cf5c8d5db65bb817a6d3cc909016dc11feb6ab9baaad44e678d60
Tx public key: 49d21aa862d8eb3349cb47acc95a7c8ed17ff9e5568922c77fde08251c1fd388
Timestamp: 1721396774 Timestamp [UCT]: 2024-07-19 13:46:14 Age [y:d:h:m:s]: 01:111:08:39:31
Block: 1069144 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 338093 RingCT/type: yes/0
Extra: 0149d21aa862d8eb3349cb47acc95a7c8ed17ff9e5568922c77fde08251c1fd38802110000000ce914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6553ca6521e13fbe7800c062532a404fdd09e8ebb1e9d9787dd79fd52f80c60d 0.600000000000 1540455 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": 1069154, "vin": [ { "gen": { "height": 1069144 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6553ca6521e13fbe7800c062532a404fdd09e8ebb1e9d9787dd79fd52f80c60d" } } ], "extra": [ 1, 73, 210, 26, 168, 98, 216, 235, 51, 73, 203, 71, 172, 201, 90, 124, 142, 209, 127, 249, 229, 86, 137, 34, 199, 127, 222, 8, 37, 28, 31, 211, 136, 2, 17, 0, 0, 0, 12, 233, 20, 221, 21, 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