Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc864738da2c56dd7785c84de4ba544cd4329da3b81a903aee1fce1b0a471c38

Tx prefix hash: d22dced2a8f57da6c0a8919ff1e3a0b9e5fc24b68ab8d1b19420d2e1c93603fe
Tx public key: d6e82752d8e8bec1cedfb74f8d2217dd9b55dc6aea1f3bd58af674f6e5220dbc
Timestamp: 1707852152 Timestamp [UCT]: 2024-02-13 19:22:32 Age [y:d:h:m:s]: 01:053:07:15:33
Block: 956841 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 299117 RingCT/type: yes/0
Extra: 01d6e82752d8e8bec1cedfb74f8d2217dd9b55dc6aea1f3bd58af674f6e5220dbc0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4808a01e83f0cb5339316ef52354617afc1d1e363476f65cb8302878fd8eff7b 0.600000000000 1416151 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": 956851, "vin": [ { "gen": { "height": 956841 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4808a01e83f0cb5339316ef52354617afc1d1e363476f65cb8302878fd8eff7b" } } ], "extra": [ 1, 214, 232, 39, 82, 216, 232, 190, 193, 206, 223, 183, 79, 141, 34, 23, 221, 155, 85, 220, 106, 234, 31, 59, 213, 138, 246, 116, 246, 229, 34, 13, 188, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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