Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d6708481a4c4c9ad3f5a3e26419e0aed70e8f03cd609300289d49e9ee940eb5e

Tx prefix hash: 95dbb28805688f52d4bbe1fd60e6c61ea193c7eaecc19db47096fec1dc36325b
Tx public key: 0020e8c159ec1e6c4f3a21784cc68e79ce070401b02e07c3d97d512d095899b5
Timestamp: 1731430542 Timestamp [UCT]: 2024-11-12 16:55:42 Age [y:d:h:m:s]: 00:147:11:18:17
Block: 1152226 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105225 RingCT/type: yes/0
Extra: 010020e8c159ec1e6c4f3a21784cc68e79ce070401b02e07c3d97d512d095899b502110000000201491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4d9543716bd38236824a30f94bb1f337fa1c6048e1189fef9ce22e418dea4c4c 0.600000000000 1637819 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": 1152236, "vin": [ { "gen": { "height": 1152226 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4d9543716bd38236824a30f94bb1f337fa1c6048e1189fef9ce22e418dea4c4c" } } ], "extra": [ 1, 0, 32, 232, 193, 89, 236, 30, 108, 79, 58, 33, 120, 76, 198, 142, 121, 206, 7, 4, 1, 176, 46, 7, 195, 217, 125, 81, 45, 9, 88, 153, 181, 2, 17, 0, 0, 0, 2, 1, 73, 31, 136, 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