Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fcf652154398885c5f68421aa0d7f4bc721646f145457b2c64f885274b89b0fd

Tx prefix hash: 122eb98e6e4c7d36ebb162e567df1e43f9bc7a2e40b6805de5dd441db5d34b1c
Tx public key: 459e2bc30c1bf600037847f4eed2c1c5ade08d694ac7d4a5791108cb70da0152
Timestamp: 1704793057 Timestamp [UCT]: 2024-01-09 09:37:37 Age [y:d:h:m:s]: 01:097:01:51:51
Block: 931468 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 330488 RingCT/type: yes/0
Extra: 01459e2bc30c1bf600037847f4eed2c1c5ade08d694ac7d4a5791108cb70da01520211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 37350b613a093dc6e04972c963e6013792559e7a729cb69f450c7d9c9c7bbec1 0.600000000000 1389370 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": 931478, "vin": [ { "gen": { "height": 931468 } } ], "vout": [ { "amount": 600000000, "target": { "key": "37350b613a093dc6e04972c963e6013792559e7a729cb69f450c7d9c9c7bbec1" } } ], "extra": [ 1, 69, 158, 43, 195, 12, 27, 246, 0, 3, 120, 71, 244, 238, 210, 193, 197, 173, 224, 141, 105, 74, 199, 212, 165, 121, 17, 8, 203, 112, 218, 1, 82, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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