Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 834ae8e7004cfbbfc27e3f2c82e5e3120e384a69b7e04d08bb0f090b9ddf3655

Tx prefix hash: bfb611aa5a6c9f3c3b63b7bda5b2f346f047cd31b3f96963717dbba39b96ecfd
Tx public key: 15559bedc68e7caf6d54fca421ddc354ab28b568b9fab9fd802e794541ab9487
Timestamp: 1695577896 Timestamp [UCT]: 2023-09-24 17:51:36 Age [y:d:h:m:s]: 01:186:14:05:56
Block: 855280 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 394411 RingCT/type: yes/0
Extra: 0115559bedc68e7caf6d54fca421ddc354ab28b568b9fab9fd802e794541ab9487021100000002faf35c9c000000000000000000

1 output(s) for total of 0.899709622000 dcy

stealth address amount amount idx
00: 2d9cba63b3ef210a15792a4cf72504827ff6b014a3d81d05fe54721375258a7a 0.899709622000 1309294 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": 855290, "vin": [ { "gen": { "height": 855280 } } ], "vout": [ { "amount": 899709622, "target": { "key": "2d9cba63b3ef210a15792a4cf72504827ff6b014a3d81d05fe54721375258a7a" } } ], "extra": [ 1, 21, 85, 155, 237, 198, 142, 124, 175, 109, 84, 252, 164, 33, 221, 195, 84, 171, 40, 181, 104, 185, 250, 185, 253, 128, 46, 121, 69, 65, 171, 148, 135, 2, 17, 0, 0, 0, 2, 250, 243, 92, 156, 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