Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: caba23aeb8888ad25b9e05353b8edd1364874ac6a8664fbafe66c6bbca13c57c

Tx prefix hash: 0becbe76c3069510e668a27c471157c274698c905cfb9b6f2f6807d5f471b8e4
Tx public key: 2c12ea3a54fc0b5e32dcf0dc7085f0abc1b29626d4bf6691d81800f2b37ff0cc
Timestamp: 1713831304 Timestamp [UCT]: 2024-04-23 00:15:04 Age [y:d:h:m:s]: 01:191:00:05:36
Block: 1006409 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 395161 RingCT/type: yes/0
Extra: 012c12ea3a54fc0b5e32dcf0dc7085f0abc1b29626d4bf6691d81800f2b37ff0cc0211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e5344df470e58cc4058d93dbd1bb84f44bc7b39e30797d51f77a00094175425d 0.600000000000 1467435 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": 1006419, "vin": [ { "gen": { "height": 1006409 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e5344df470e58cc4058d93dbd1bb84f44bc7b39e30797d51f77a00094175425d" } } ], "extra": [ 1, 44, 18, 234, 58, 84, 252, 11, 94, 50, 220, 240, 220, 112, 133, 240, 171, 193, 178, 150, 38, 212, 191, 102, 145, 216, 24, 0, 242, 179, 127, 240, 204, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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