Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bebaeb2c795f06267d6e285862861fca39c9c12d06101e34b7635fe8736645f7

Tx prefix hash: 360357caef3ce8e03d38996799f6d2d0b961bff129c1c84cba2bbee94bf27eb2
Tx public key: c11a7c833a89d9c56de0d1f8e8d49e2e3a65f91bf81e11f7652e8e5c49839d20
Timestamp: 1575131966 Timestamp [UCT]: 2019-11-30 16:39:26 Age [y:d:h:m:s]: 05:139:13:25:07
Block: 20932 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1242301 RingCT/type: yes/0
Extra: 01c11a7c833a89d9c56de0d1f8e8d49e2e3a65f91bf81e11f7652e8e5c49839d200211000000029159db1e000000000000000000

1 output(s) for total of 523.171972947000 dcy

stealth address amount amount idx
00: b1bc196ae4624ee80ba0b50efd4d03b0d4838cf1bdb6cf7ac6dbcb5130035033 523.171972947000 33419 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": 20942, "vin": [ { "gen": { "height": 20932 } } ], "vout": [ { "amount": 523171972947, "target": { "key": "b1bc196ae4624ee80ba0b50efd4d03b0d4838cf1bdb6cf7ac6dbcb5130035033" } } ], "extra": [ 1, 193, 26, 124, 131, 58, 137, 217, 197, 109, 224, 209, 248, 232, 212, 158, 46, 58, 101, 249, 27, 248, 30, 17, 247, 101, 46, 142, 92, 73, 131, 157, 32, 2, 17, 0, 0, 0, 2, 145, 89, 219, 30, 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