Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 419f414943e38428a6f59999ed5169ec06a1efc53c19faf7c8228e2504d75681

Tx prefix hash: a4bcbd5cab49f7a0ad62d9a37a00a2a841e14b6aff9960bccb9cc7d2652b96ce
Tx public key: a2a1851b80c0c4a222e668c821294227cc53fbc5b8ec7d2548d7ecc62adab71f
Timestamp: 1738179780 Timestamp [UCT]: 2025-01-29 19:43:00 Age [y:d:h:m:s]: 00:341:00:34:51
Block: 1207866 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 241561 RingCT/type: yes/0
Extra: 01a2a1851b80c0c4a222e668c821294227cc53fbc5b8ec7d2548d7ecc62adab71f0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7405c7c82943ff3d0abad8e468cc05d61c8d05937eed1d1b51130fdabcb82ada 0.600000000000 1694593 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": 1207876, "vin": [ { "gen": { "height": 1207866 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7405c7c82943ff3d0abad8e468cc05d61c8d05937eed1d1b51130fdabcb82ada" } } ], "extra": [ 1, 162, 161, 133, 27, 128, 192, 196, 162, 34, 230, 104, 200, 33, 41, 66, 39, 204, 83, 251, 197, 184, 236, 125, 37, 72, 215, 236, 198, 42, 218, 183, 31, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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