Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a824f9ed2a719432b84e7ed5f4f08792e1c17373e350cfda2ac7508d53947cca

Tx prefix hash: 9e43ea413d70111394429b9e378177b74a27bace69b3f0ef9c64ee623d8b39f3
Tx public key: dd34b7e51bb0db8e5dd848b1fb5ec9b9e1a4ccc4f1cf364f9d79ebb5f26701dc
Timestamp: 1673379810 Timestamp [UCT]: 2023-01-10 19:43:30 Age [y:d:h:m:s]: 02:066:15:37:44
Block: 671910 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 569332 RingCT/type: yes/0
Extra: 01dd34b7e51bb0db8e5dd848b1fb5ec9b9e1a4ccc4f1cf364f9d79ebb5f26701dc0211000000018b7b6602000000000000000000

1 output(s) for total of 3.644879720000 dcy

stealth address amount amount idx
00: 1dbdbca8067d23b4667a1dbb405353f8e703d916c49bb84fcfefc5da66c040ad 3.644879720000 1113421 of 0

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": 671920, "vin": [ { "gen": { "height": 671910 } } ], "vout": [ { "amount": 3644879720, "target": { "key": "1dbdbca8067d23b4667a1dbb405353f8e703d916c49bb84fcfefc5da66c040ad" } } ], "extra": [ 1, 221, 52, 183, 229, 27, 176, 219, 142, 93, 216, 72, 177, 251, 94, 201, 185, 225, 164, 204, 196, 241, 207, 54, 79, 157, 121, 235, 181, 242, 103, 1, 220, 2, 17, 0, 0, 0, 1, 139, 123, 102, 2, 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