Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b96c548b8e72976f3d0a3f0165b770bdbb5cdc536dfae8cb0ec0c1668e88a8b6

Tx prefix hash: bf64e2ff18e9fd674f271eeca731e117cf1705938c012d4123f6314089763eb8
Tx public key: adc0747773e9d0dcefa63aedd54d089b0de2af2e0ad56c299172cc1657628f17
Timestamp: 1711390343 Timestamp [UCT]: 2024-03-25 18:12:23 Age [y:d:h:m:s]: 01:083:14:25:53
Block: 986203 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 320639 RingCT/type: yes/0
Extra: 01adc0747773e9d0dcefa63aedd54d089b0de2af2e0ad56c299172cc1657628f1702110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cd9504ac17c98f4f0384c43a95b56dd21082c07a7c67e4a0c3fe09e2fb1d8014 0.600000000000 1446430 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": 986213, "vin": [ { "gen": { "height": 986203 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cd9504ac17c98f4f0384c43a95b56dd21082c07a7c67e4a0c3fe09e2fb1d8014" } } ], "extra": [ 1, 173, 192, 116, 119, 115, 233, 208, 220, 239, 166, 58, 237, 213, 77, 8, 155, 13, 226, 175, 46, 10, 213, 108, 41, 145, 114, 204, 22, 87, 98, 143, 23, 2, 17, 0, 0, 0, 5, 82, 212, 126, 148, 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