Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 00fc2fc0cffa1ce7a49fb5739dc6c9475cc90a3ebad4898edb855abcb537facb

Tx prefix hash: be903c8080f0df297f029e2721b2c08f9543ad77554f62b5e1a0b0006a920aba
Tx public key: 123766b037d3c16b5a2a6187a2fb18372c29fc86d81e8875cc27bb0e75554437
Timestamp: 1700812017 Timestamp [UCT]: 2023-11-24 07:46:57 Age [y:d:h:m:s]: 01:173:21:28:53
Block: 898479 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 385456 RingCT/type: yes/0
Extra: 01123766b037d3c16b5a2a6187a2fb18372c29fc86d81e8875cc27bb0e7555443702110000000833af99f4000000000000000000

1 output(s) for total of 0.647092077000 dcy

stealth address amount amount idx
00: 5c09311d604e729d5e1a265857cad3cfd829e3463f44ee4108aebbf49dfb32da 0.647092077000 1354898 of 0

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": 898489, "vin": [ { "gen": { "height": 898479 } } ], "vout": [ { "amount": 647092077, "target": { "key": "5c09311d604e729d5e1a265857cad3cfd829e3463f44ee4108aebbf49dfb32da" } } ], "extra": [ 1, 18, 55, 102, 176, 55, 211, 193, 107, 90, 42, 97, 135, 162, 251, 24, 55, 44, 41, 252, 134, 216, 30, 136, 117, 204, 39, 187, 14, 117, 85, 68, 55, 2, 17, 0, 0, 0, 8, 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