Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 91b55c55edfe03d91fcef5b088201c20a7e190bedddb61c177e3d6fdbf06b57e

Tx prefix hash: 4d92b7acb49737c5195ed80c0c632a87b6f228d392de4bef054a2156b14fe2c0
Tx public key: 00c4c65e548eeb39388fff93b0a5ed4f344bc1f272c0c8a4c9ed360aa85bd9bd
Timestamp: 1760610126 Timestamp [UCT]: 2025-10-16 10:22:06 Age [y:d:h:m:s]: 00:081:12:36:33
Block: 1391121 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 58390 RingCT/type: yes/0
Extra: 0100c4c65e548eeb39388fff93b0a5ed4f344bc1f272c0c8a4c9ed360aa85bd9bd0211000000042609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7c33ed8d78bf3526ea6713731412f497c78b9517c75f97bc1ecf064b1436e459 0.600000000000 1879368 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": 1391131, "vin": [ { "gen": { "height": 1391121 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7c33ed8d78bf3526ea6713731412f497c78b9517c75f97bc1ecf064b1436e459" } } ], "extra": [ 1, 0, 196, 198, 94, 84, 142, 235, 57, 56, 143, 255, 147, 176, 165, 237, 79, 52, 75, 193, 242, 114, 192, 200, 164, 201, 237, 54, 10, 168, 91, 217, 189, 2, 17, 0, 0, 0, 4, 38, 9, 179, 160, 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