Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3ad94f9193908ca45645d70a7411ed52703277aa4547b64c2721b1f21ff996bd

Tx prefix hash: 1c07747951af2ca3ad46cee9116523eaf0bdf97d3a4c7515ec35159d3310c10d
Tx public key: a8fafdcc090cb8e52127c68eb2e5b547e9f46bee2d2579e02c1bb6905c8b9bed
Timestamp: 1745353951 Timestamp [UCT]: 2025-04-22 20:32:31 Age [y:d:h:m:s]: 00:210:19:21:44
Block: 1267236 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 148387 RingCT/type: yes/0
Extra: 01a8fafdcc090cb8e52127c68eb2e5b547e9f46bee2d2579e02c1bb6905c8b9bed021100000002dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 89edf971de0b5c63fc3b422e8367173cbf35c3a163cd4c3edde40c85086ae4e1 0.600000000000 1754463 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": 1267246, "vin": [ { "gen": { "height": 1267236 } } ], "vout": [ { "amount": 600000000, "target": { "key": "89edf971de0b5c63fc3b422e8367173cbf35c3a163cd4c3edde40c85086ae4e1" } } ], "extra": [ 1, 168, 250, 253, 204, 9, 12, 184, 229, 33, 39, 198, 142, 178, 229, 181, 71, 233, 244, 107, 238, 45, 37, 121, 224, 44, 27, 182, 144, 92, 139, 155, 237, 2, 17, 0, 0, 0, 2, 219, 181, 113, 193, 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