Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f5453abd0287d920cb7668ca51d4cd3dfe17b3602f3bba07d98cabf30be718c8

Tx prefix hash: 429c03553e08e1d0fd70080c9936ed72a51fa618e67536d15d249386b365b84b
Tx public key: f5e6ea10d265ee664ac8e2b033080fd0dea778cd193a4db6c5a73f74ddb7297a
Timestamp: 1723485829 Timestamp [UCT]: 2024-08-12 18:03:49 Age [y:d:h:m:s]: 00:239:17:02:45
Block: 1086452 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 171211 RingCT/type: yes/0
Extra: 01f5e6ea10d265ee664ac8e2b033080fd0dea778cd193a4db6c5a73f74ddb7297a021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 242e92a9878cf0bd0bf4eb5c86cd0cf2e21bdd455018722f6e60edb8f7a908c2 0.600000000000 1561049 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": 1086462, "vin": [ { "gen": { "height": 1086452 } } ], "vout": [ { "amount": 600000000, "target": { "key": "242e92a9878cf0bd0bf4eb5c86cd0cf2e21bdd455018722f6e60edb8f7a908c2" } } ], "extra": [ 1, 245, 230, 234, 16, 210, 101, 238, 102, 74, 200, 226, 176, 51, 8, 15, 208, 222, 167, 120, 205, 25, 58, 77, 182, 197, 167, 63, 116, 221, 183, 41, 122, 2, 17, 0, 0, 0, 4, 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