Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 63e4ac21dc1276b02e537426603e1cf854263d110c501a07c90b57255410e71f

Tx prefix hash: 0d4a4a5933d8f6b53f1f4b63b182ec4d1352bad1feae7974f416eeaf4792987d
Tx public key: 579f9ef1864254ae2ebc75dadf67522a247f67d68fead3347cbf571b3f72f8c4
Timestamp: 1710184632 Timestamp [UCT]: 2024-03-11 19:17:12 Age [y:d:h:m:s]: 00:349:23:33:43
Block: 976195 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 250207 RingCT/type: yes/0
Extra: 01579f9ef1864254ae2ebc75dadf67522a247f67d68fead3347cbf571b3f72f8c402110000000b0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d89aa88046dac5043e7c52aa23991beeb7397cf47a91a64c5c7e48448c4fb0b7 0.600000000000 1436186 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": 976205, "vin": [ { "gen": { "height": 976195 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d89aa88046dac5043e7c52aa23991beeb7397cf47a91a64c5c7e48448c4fb0b7" } } ], "extra": [ 1, 87, 159, 158, 241, 134, 66, 84, 174, 46, 188, 117, 218, 223, 103, 82, 42, 36, 127, 103, 214, 143, 234, 211, 52, 124, 191, 87, 27, 63, 114, 248, 196, 2, 17, 0, 0, 0, 11, 0, 17, 5, 91, 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