Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b6e02e36f21bd9707671cec8dd7c591f1cfe93cb37387c7fcac2187685c59239

Tx prefix hash: 8919d357036085dbfd1a7b6c9e95a434a204d0d4421476204c8b958361ac80c2
Tx public key: 33c4e88e55fdf30f272950988ed6beed1a5b01c157a89cc7cc4f478c9b50b428
Timestamp: 1694093574 Timestamp [UCT]: 2023-09-07 13:32:54 Age [y:d:h:m:s]: 01:272:05:19:06
Block: 842967 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 455699 RingCT/type: yes/0
Extra: 0133c4e88e55fdf30f272950988ed6beed1a5b01c157a89cc7cc4f478c9b50b42802110000000333af99f4000000000000000000

1 output(s) for total of 0.988326553000 dcy

stealth address amount amount idx
00: a3693847eb8f80c4fa6735b819e3d3dfe28a06226cd8965671311d321db839db 0.988326553000 1296147 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": 842977, "vin": [ { "gen": { "height": 842967 } } ], "vout": [ { "amount": 988326553, "target": { "key": "a3693847eb8f80c4fa6735b819e3d3dfe28a06226cd8965671311d321db839db" } } ], "extra": [ 1, 51, 196, 232, 142, 85, 253, 243, 15, 39, 41, 80, 152, 142, 214, 190, 237, 26, 91, 1, 193, 87, 168, 156, 199, 204, 79, 71, 140, 155, 80, 180, 40, 2, 17, 0, 0, 0, 3, 51, 175, 153, 244, 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