Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f29c0530e155dd5fc4d006f4ef36dcc250509e828d22ae76ef2632d7147bf5a8

Tx prefix hash: cf73640084c97cb49c848eb843e5445e41a66f2dc7ff1e5434a881c7ee148557
Tx public key: 429eb071e24d3e57ec48f8d2b4b31a44357cbabeee63894baf8a106c4969abae
Timestamp: 1714629297 Timestamp [UCT]: 2024-05-02 05:54:57 Age [y:d:h:m:s]: 01:023:11:24:21
Block: 1013029 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 277731 RingCT/type: yes/0
Extra: 01429eb071e24d3e57ec48f8d2b4b31a44357cbabeee63894baf8a106c4969abae02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a7d7cace66fb0bef7c0c28f562d674af1d7a586922d0b6ebe0b579a38cad58fc 0.600000000000 1475734 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": 1013039, "vin": [ { "gen": { "height": 1013029 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a7d7cace66fb0bef7c0c28f562d674af1d7a586922d0b6ebe0b579a38cad58fc" } } ], "extra": [ 1, 66, 158, 176, 113, 226, 77, 62, 87, 236, 72, 248, 210, 180, 179, 26, 68, 53, 124, 186, 190, 238, 99, 137, 75, 175, 138, 16, 108, 73, 105, 171, 174, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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