Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 78dcc747296717ac60768f8040a91d53f15292ab37568ef8d0464e6f37d35d45

Tx prefix hash: 39697b8af0e8f7a62a2ed8c9a9586a47edb4d8539042c18200e3fc591556600a
Tx public key: 6592ffd4138c13da556e68e4a07c5a260dfbc78c7596c3d32f1b30e6020574f4
Timestamp: 1725111811 Timestamp [UCT]: 2024-08-31 13:43:31 Age [y:d:h:m:s]: 00:230:01:03:59
Block: 1099932 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 164280 RingCT/type: yes/0
Extra: 016592ffd4138c13da556e68e4a07c5a260dfbc78c7596c3d32f1b30e6020574f402110000000891e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 42678b9af920d2555af5d8947880c0d6fb0e7f0184eb9dae8e1d4c268e87bba1 0.600000000000 1575901 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": 1099942, "vin": [ { "gen": { "height": 1099932 } } ], "vout": [ { "amount": 600000000, "target": { "key": "42678b9af920d2555af5d8947880c0d6fb0e7f0184eb9dae8e1d4c268e87bba1" } } ], "extra": [ 1, 101, 146, 255, 212, 19, 140, 19, 218, 85, 110, 104, 228, 160, 124, 90, 38, 13, 251, 199, 140, 117, 150, 195, 211, 47, 27, 48, 230, 2, 5, 116, 244, 2, 17, 0, 0, 0, 8, 145, 225, 60, 4, 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