Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4c1503e200bd2df815c6b7567720f01b35f44255c9ce4ac6d186033cae7ec939

Tx prefix hash: efd6a34fbc29dfa5194bda1cd81b8f4dcc601c464e80997e04dbcf5f3b7e5b8f
Tx public key: 4d973807b3c49d2b9026c97818449118cf7120635202bd9da9499cfb3c41570e
Timestamp: 1723577073 Timestamp [UCT]: 2024-08-13 19:24:33 Age [y:d:h:m:s]: 00:246:10:05:42
Block: 1087210 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175995 RingCT/type: yes/0
Extra: 014d973807b3c49d2b9026c97818449118cf7120635202bd9da9499cfb3c41570e021100000011e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 680757f79ecd0f00a925cc565a732f5dc197ab9ffb6e68f64433e8e8533f8eb6 0.600000000000 1561815 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": 1087220, "vin": [ { "gen": { "height": 1087210 } } ], "vout": [ { "amount": 600000000, "target": { "key": "680757f79ecd0f00a925cc565a732f5dc197ab9ffb6e68f64433e8e8533f8eb6" } } ], "extra": [ 1, 77, 151, 56, 7, 179, 196, 157, 43, 144, 38, 201, 120, 24, 68, 145, 24, 207, 113, 32, 99, 82, 2, 189, 157, 169, 73, 156, 251, 60, 65, 87, 14, 2, 17, 0, 0, 0, 17, 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