Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 07ad207c6093948b49c0d64fb6cccc20978e71d6e350ace9fc4fd89fd889f8e6

Tx prefix hash: ac20f91c7251de5c320c1ed14ff3023f9d184294b3bae655ab58f44c0a9ee2cf
Tx public key: fd47e3075bc998a7934e179b66e8ade9be39f21bdfb160e4c4a89e553b697c83
Timestamp: 1583346209 Timestamp [UCT]: 2020-03-04 18:23:29 Age [y:d:h:m:s]: 05:000:17:39:44
Block: 76328 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1155613 RingCT/type: yes/0
Extra: 01fd47e3075bc998a7934e179b66e8ade9be39f21bdfb160e4c4a89e553b697c8302110000000356c366d3000000000000000000

1 output(s) for total of 342.842336399000 dcy

stealth address amount amount idx
00: bfd76b1ccfa22d65d8db845b44c3892e1554d082c0965d3ac38616ab6cbee31b 342.842336399000 140569 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": 76338, "vin": [ { "gen": { "height": 76328 } } ], "vout": [ { "amount": 342842336399, "target": { "key": "bfd76b1ccfa22d65d8db845b44c3892e1554d082c0965d3ac38616ab6cbee31b" } } ], "extra": [ 1, 253, 71, 227, 7, 91, 201, 152, 167, 147, 78, 23, 155, 102, 232, 173, 233, 190, 57, 242, 27, 223, 177, 96, 228, 196, 168, 158, 85, 59, 105, 124, 131, 2, 17, 0, 0, 0, 3, 86, 195, 102, 211, 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