Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8c8df47bd6ead6547e8391976c86816fcc0ab1b7b3ba98e0e27baf29908869a0

Tx prefix hash: c0b4894e914c1b58b046bf2cbdab688df7fc9954c60c39771ddbff3bc7725024
Tx public key: b45e802b0f70942038c9c0c5e33a86e90263084312e43cb6f68376cdbeda63c3
Timestamp: 1702156790 Timestamp [UCT]: 2023-12-09 21:19:50 Age [y:d:h:m:s]: 01:052:17:55:41
Block: 909631 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 298803 RingCT/type: yes/0
Extra: 01b45e802b0f70942038c9c0c5e33a86e90263084312e43cb6f68376cdbeda63c302110000000133af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 32160ceca82362c6581f6547e85dba8b9a5fa87975f4d0bf3975df92a731c7f3 0.600000000000 1366734 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": 909641, "vin": [ { "gen": { "height": 909631 } } ], "vout": [ { "amount": 600000000, "target": { "key": "32160ceca82362c6581f6547e85dba8b9a5fa87975f4d0bf3975df92a731c7f3" } } ], "extra": [ 1, 180, 94, 128, 43, 15, 112, 148, 32, 56, 201, 192, 197, 227, 58, 134, 233, 2, 99, 8, 67, 18, 228, 60, 182, 246, 131, 118, 205, 190, 218, 99, 195, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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