Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d0b6025387eaed9c3ef236ef8eb0c85bda72cff68ece7de474c145e7c57cdaf

Tx prefix hash: 84212f940cd57fff3ba88dc1fc160b5519cea9b31b944a7b5d0fa814e2962e03
Tx public key: 44a54e8e07e2a852d25d4bec2ad9550b78fa7d713333fcb8130e2e378fcc05fe
Timestamp: 1720686324 Timestamp [UCT]: 2024-07-11 08:25:24 Age [y:d:h:m:s]: 00:183:05:08:21
Block: 1063258 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 131084 RingCT/type: yes/0
Extra: 0144a54e8e07e2a852d25d4bec2ad9550b78fa7d713333fcb8130e2e378fcc05fe021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 172f5bccb99cf45a06326ff19eabc7da309e02db4bb46ad05e3e55f93901b6f1 0.600000000000 1533773 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": 1063268, "vin": [ { "gen": { "height": 1063258 } } ], "vout": [ { "amount": 600000000, "target": { "key": "172f5bccb99cf45a06326ff19eabc7da309e02db4bb46ad05e3e55f93901b6f1" } } ], "extra": [ 1, 68, 165, 78, 142, 7, 226, 168, 82, 210, 93, 75, 236, 42, 217, 85, 11, 120, 250, 125, 113, 51, 51, 252, 184, 19, 14, 46, 55, 143, 204, 5, 254, 2, 17, 0, 0, 0, 3, 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