Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b4b5b3fb4531d369ee5b3fd736d5197550b6fad85f2130987a0fcda0cda803da

Tx prefix hash: 7390255ca70e3636b5bf7fab2c9c89ffdbec581c9c763257d17176abda4910d8
Tx public key: c1fe608fe30c8c42f2636bd9be05a0026ffaa2d3a5c802ed38b264b74867f4e3
Timestamp: 1736394766 Timestamp [UCT]: 2025-01-09 03:52:46 Age [y:d:h:m:s]: 00:087:09:49:36
Block: 1193335 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 62245 RingCT/type: yes/0
Extra: 01c1fe608fe30c8c42f2636bd9be05a0026ffaa2d3a5c802ed38b264b74867f4e3021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 79ceea29c15c1eb61cc39fff98c92b2b41b53da17c04e582ce14a3c8680759aa 0.600000000000 1679894 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": 1193345, "vin": [ { "gen": { "height": 1193335 } } ], "vout": [ { "amount": 600000000, "target": { "key": "79ceea29c15c1eb61cc39fff98c92b2b41b53da17c04e582ce14a3c8680759aa" } } ], "extra": [ 1, 193, 254, 96, 143, 227, 12, 140, 66, 242, 99, 107, 217, 190, 5, 160, 2, 111, 250, 162, 211, 165, 200, 2, 237, 56, 178, 100, 183, 72, 103, 244, 227, 2, 17, 0, 0, 0, 3, 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