Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d3a3c79c0dfee48f8d391a28f570114e59d97f64db9ee246a335b3efc46f6af6

Tx prefix hash: c2793760cee7676a0cce678b1412b15ce493073dbbfca1c7e1d7af5bf6b0c199
Tx public key: 1e49b03e44019539b78afc9825c12e7ce50654b8465fae5a3ad330c000946de6
Timestamp: 1731521304 Timestamp [UCT]: 2024-11-13 18:08:24 Age [y:d:h:m:s]: 00:143:22:02:18
Block: 1152979 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102681 RingCT/type: yes/0
Extra: 011e49b03e44019539b78afc9825c12e7ce50654b8465fae5a3ad330c000946de6021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9e5eb1c3c453a50e1982db49cb58914e536587081ebf24d7d32931a8ba9033d4 0.600000000000 1638586 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": 1152989, "vin": [ { "gen": { "height": 1152979 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9e5eb1c3c453a50e1982db49cb58914e536587081ebf24d7d32931a8ba9033d4" } } ], "extra": [ 1, 30, 73, 176, 62, 68, 1, 149, 57, 183, 138, 252, 152, 37, 193, 46, 124, 229, 6, 84, 184, 70, 95, 174, 90, 58, 211, 48, 192, 0, 148, 109, 230, 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