Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 006e7b4f4cedf05019952c6d2aeb6268f52916744a9b9f0e3833ca2ed74bd967

Tx prefix hash: 171b691a6eafd9b7b2cf302ed74fbd9184a1646a3a0e70bb0b0687dab6cb1ea1
Tx public key: 0126e9ce10abbf3da1be1f7e7d0be20d25f3b87833194c87e99de7710c2c16ea
Timestamp: 1659317380 Timestamp [UCT]: 2022-08-01 01:29:40 Age [y:d:h:m:s]: 02:101:19:35:38
Block: 556057 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 594155 RingCT/type: yes/0
Extra: 010126e9ce10abbf3da1be1f7e7d0be20d25f3b87833194c87e99de7710c2c16ea021100000003ec6d1a1a000000000000000000

1 output(s) for total of 8.821703403000 dcy

stealth address amount amount idx
00: 21841d2f7e6794b3e74114fea2b09502eed91452dc09b2c82715a89541e52277 8.821703403000 987981 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": 556067, "vin": [ { "gen": { "height": 556057 } } ], "vout": [ { "amount": 8821703403, "target": { "key": "21841d2f7e6794b3e74114fea2b09502eed91452dc09b2c82715a89541e52277" } } ], "extra": [ 1, 1, 38, 233, 206, 16, 171, 191, 61, 161, 190, 31, 126, 125, 11, 226, 13, 37, 243, 184, 120, 51, 25, 76, 135, 233, 157, 231, 113, 12, 44, 22, 234, 2, 17, 0, 0, 0, 3, 236, 109, 26, 26, 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