Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f03cb70e039eff12ac70b705f25c1131edd8de8a14004af81dbdc9e7b06ed49b

Tx prefix hash: 72594b9e9ddce8ea36fb96a40d3be36cd412a8dea175a56e80bd7a53889a7edf
Tx public key: 6ee2fb83dd9144f4af66110325a6fc9989fe61fda4b5b51275b7bbdfcb177474
Timestamp: 1673068933 Timestamp [UCT]: 2023-01-07 05:22:13 Age [y:d:h:m:s]: 01:330:03:16:33
Block: 669329 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 496969 RingCT/type: yes/0
Extra: 016ee2fb83dd9144f4af66110325a6fc9989fe61fda4b5b51275b7bbdfcb17747402110000000352542ceb000000000000000000

1 output(s) for total of 3.717364349000 dcy

stealth address amount amount idx
00: 9f73a272b1ece5234ebcffff3ae0c6bb48bfa5e5f5f897a724a19de932cefe50 3.717364349000 1110636 of 0

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": 669339, "vin": [ { "gen": { "height": 669329 } } ], "vout": [ { "amount": 3717364349, "target": { "key": "9f73a272b1ece5234ebcffff3ae0c6bb48bfa5e5f5f897a724a19de932cefe50" } } ], "extra": [ 1, 110, 226, 251, 131, 221, 145, 68, 244, 175, 102, 17, 3, 37, 166, 252, 153, 137, 254, 97, 253, 164, 181, 181, 18, 117, 183, 187, 223, 203, 23, 116, 116, 2, 17, 0, 0, 0, 3, 82, 84, 44, 235, 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