Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 013d13ed0b939422bedddf56ae61d70c58e322acb1613f74d2baf0de05d00437

Tx prefix hash: a83903134a46672e647d5ddfc66f1d379a844fe1a9c8d605e9e9be4980507c3d
Tx public key: 7c7dcf1ba58b807b91c38d099ca9b093036d65c22ff2646427c8ce4c36f27779
Timestamp: 1721142460 Timestamp [UCT]: 2024-07-16 15:07:40 Age [y:d:h:m:s]: 00:259:13:23:41
Block: 1067039 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 185407 RingCT/type: yes/0
Extra: 017c7dcf1ba58b807b91c38d099ca9b093036d65c22ff2646427c8ce4c36f27779021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: acf7acee09f21723aa1cba710761d4f1824a8b4e61206d62f4efbed8e48795ec 0.600000000000 1537744 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": 1067049, "vin": [ { "gen": { "height": 1067039 } } ], "vout": [ { "amount": 600000000, "target": { "key": "acf7acee09f21723aa1cba710761d4f1824a8b4e61206d62f4efbed8e48795ec" } } ], "extra": [ 1, 124, 125, 207, 27, 165, 139, 128, 123, 145, 195, 141, 9, 156, 169, 176, 147, 3, 109, 101, 194, 47, 242, 100, 100, 39, 200, 206, 76, 54, 242, 119, 121, 2, 17, 0, 0, 0, 5, 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