Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aff65ca82392e8db423ac1dba45a4cc2a4a9e3d4323ce91b7f351d95f1c425df

Tx prefix hash: 644bd292099ce669abb9e82b034bf208e6064dc4f6e2b3c791e022cf042018b6
Tx public key: 179293c5abd8fc9a5705e885c189e6c4308246a3a88638bc9b07567bcb093f7c
Timestamp: 1744458781 Timestamp [UCT]: 2025-04-12 11:53:01 Age [y:d:h:m:s]: 00:291:22:48:12
Block: 1259829 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 206302 RingCT/type: yes/0
Extra: 01179293c5abd8fc9a5705e885c189e6c4308246a3a88638bc9b07567bcb093f7c0211000000096c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8d38ed6c657588c8339caec96b8212b44e89ea6ab1e06cc08f8fffa3fca743ac 0.600000000000 1746978 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": 1259839, "vin": [ { "gen": { "height": 1259829 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8d38ed6c657588c8339caec96b8212b44e89ea6ab1e06cc08f8fffa3fca743ac" } } ], "extra": [ 1, 23, 146, 147, 197, 171, 216, 252, 154, 87, 5, 232, 133, 193, 137, 230, 196, 48, 130, 70, 163, 168, 134, 56, 188, 155, 7, 86, 123, 203, 9, 63, 124, 2, 17, 0, 0, 0, 9, 108, 152, 170, 61, 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