Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 479c74927fb359c76c522f5d6886d1d324a0d089df072b32bed560dcbf24c643

Tx prefix hash: 624f0517a849d3336965a28cf615f53d6d05deaa1269dea2bf7ca2bdcf8c1d52
Tx public key: 814b818cb7dd2395c0bea4732241ee5753dd1eedd2e788f5c64c320610642109
Timestamp: 1697445507 Timestamp [UCT]: 2023-10-16 08:38:27 Age [y:d:h:m:s]: 01:246:05:32:33
Block: 870772 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 436924 RingCT/type: yes/0
Extra: 01814b818cb7dd2395c0bea4732241ee5753dd1eedd2e788f5c64c3206106421090211000000014b8f5122000000000000000000

1 output(s) for total of 0.799412465000 dcy

stealth address amount amount idx
00: f3353777cc0293697dbe35fa73786ecea165241fcd48f0994db29a796101a8c3 0.799412465000 1325659 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": 870782, "vin": [ { "gen": { "height": 870772 } } ], "vout": [ { "amount": 799412465, "target": { "key": "f3353777cc0293697dbe35fa73786ecea165241fcd48f0994db29a796101a8c3" } } ], "extra": [ 1, 129, 75, 129, 140, 183, 221, 35, 149, 192, 190, 164, 115, 34, 65, 238, 87, 83, 221, 30, 237, 210, 231, 136, 245, 198, 76, 50, 6, 16, 100, 33, 9, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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