Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e865264dfcc9b1bbdde9522a4d5b5a0b44dda4f6f62530afe0c01c837cfc1a78

Tx prefix hash: 4a2b15c220a631df49fe8c5d1eb4c774c1d97022b168d09c695200a6dca4cabe
Tx public key: 6afbc69a712ec74852e3e8ec008d4101ca18402835db01640d5c3d24c9af1885
Timestamp: 1731687041 Timestamp [UCT]: 2024-11-15 16:10:41 Age [y:d:h:m:s]: 00:213:23:49:32
Block: 1154348 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 152703 RingCT/type: yes/0
Extra: 016afbc69a712ec74852e3e8ec008d4101ca18402835db01640d5c3d24c9af1885021100000009007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f51d24d242ebdd003bbe386c34096fc19e01b6de343e1332dc44b8e64a69eafc 0.600000000000 1639959 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": 1154358, "vin": [ { "gen": { "height": 1154348 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f51d24d242ebdd003bbe386c34096fc19e01b6de343e1332dc44b8e64a69eafc" } } ], "extra": [ 1, 106, 251, 198, 154, 113, 46, 199, 72, 82, 227, 232, 236, 0, 141, 65, 1, 202, 24, 64, 40, 53, 219, 1, 100, 13, 92, 61, 36, 201, 175, 24, 133, 2, 17, 0, 0, 0, 9, 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