Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f2cf45ca1cb0967fbb8d029dfd0b4436ac0555c3e745722a5537fa256f88dfa0

Tx prefix hash: 5ec4c108ccc019eb07742b958d3cae9f8b3e5e810390e2921f2e58291d205be8
Tx public key: 798e368ddf095634f80831e6c4c571b783ab506c8f36b79270f9f75f72f73c83
Timestamp: 1732306120 Timestamp [UCT]: 2024-11-22 20:08:40 Age [y:d:h:m:s]: 00:205:19:53:37
Block: 1159486 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 146862 RingCT/type: yes/0
Extra: 01798e368ddf095634f80831e6c4c571b783ab506c8f36b79270f9f75f72f73c83021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 135fff5e27cac3a6d0026df7b9c40087349958f3bb38e707039895e4dc92b4a5 0.600000000000 1645123 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": 1159496, "vin": [ { "gen": { "height": 1159486 } } ], "vout": [ { "amount": 600000000, "target": { "key": "135fff5e27cac3a6d0026df7b9c40087349958f3bb38e707039895e4dc92b4a5" } } ], "extra": [ 1, 121, 142, 54, 141, 223, 9, 86, 52, 248, 8, 49, 230, 196, 197, 113, 183, 131, 171, 80, 108, 143, 54, 183, 146, 112, 249, 247, 95, 114, 247, 60, 131, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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