Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b0899efb3caf450bc5e2bf8d577e1a7985db4d93f54ac7954aa6be0e3438df54

Tx prefix hash: 621381828f5b184fb898f3f32ff86848f438506b6c931737c2c9479704d4910c
Tx public key: fb048bf3b6e793845ecd7e789111eb1e3ad49455456bb1d0cec7dbf76115e5e6
Timestamp: 1746165455 Timestamp [UCT]: 2025-05-02 05:57:35 Age [y:d:h:m:s]: 00:203:00:41:25
Block: 1273956 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 142809 RingCT/type: yes/0
Extra: 01fb048bf3b6e793845ecd7e789111eb1e3ad49455456bb1d0cec7dbf76115e5e602110000000301491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7046def1e7aa1889062ec1f6c1f953c7198e31f16c8b487450e1b64f36e1bf70 0.600000000000 1761243 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": 1273966, "vin": [ { "gen": { "height": 1273956 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7046def1e7aa1889062ec1f6c1f953c7198e31f16c8b487450e1b64f36e1bf70" } } ], "extra": [ 1, 251, 4, 139, 243, 182, 231, 147, 132, 94, 205, 126, 120, 145, 17, 235, 30, 58, 212, 148, 85, 69, 107, 177, 208, 206, 199, 219, 247, 97, 21, 229, 230, 2, 17, 0, 0, 0, 3, 1, 73, 31, 136, 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