Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 73592bdaba63f06449f229ec07dfe29592df53b11d70e5e50e6640a03ee2eab2

Tx prefix hash: dc48199cc3c950cae8bc626db0991f9b396f2b708d31c4a94579d4da4966c2a5
Tx public key: 340019294a7d265fee3598adc31166b5975d9e323efcbd6de5b0a30be5c475c1
Timestamp: 1733478704 Timestamp [UCT]: 2024-12-06 09:51:44 Age [y:d:h:m:s]: 00:109:12:14:47
Block: 1169204 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 78051 RingCT/type: yes/0
Extra: 01340019294a7d265fee3598adc31166b5975d9e323efcbd6de5b0a30be5c475c10211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 41f5c32bf7b304026b23d4cbcfccd500499ae7f5f5a82379ac60d17f613b0e1b 0.600000000000 1654919 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": 1169214, "vin": [ { "gen": { "height": 1169204 } } ], "vout": [ { "amount": 600000000, "target": { "key": "41f5c32bf7b304026b23d4cbcfccd500499ae7f5f5a82379ac60d17f613b0e1b" } } ], "extra": [ 1, 52, 0, 25, 41, 74, 125, 38, 95, 238, 53, 152, 173, 195, 17, 102, 181, 151, 93, 158, 50, 62, 252, 189, 109, 229, 176, 163, 11, 229, 196, 117, 193, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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