Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fd547ea5fb480adffe69579fd2c56c339d646f2b5eec7abcb92d77e046801937

Tx prefix hash: fa7a1f82645d94d5e0bf0896fe8edc4afc6a03036bd422339f6492bbad328303
Tx public key: 0a0d6da1759965b5569c0e3c4bc65a4ba5d375d170eb95d85f6c68c63d212f90
Timestamp: 1761363077 Timestamp [UCT]: 2025-10-25 03:31:17 Age [y:d:h:m:s]: 00:016:21:43:36
Block: 1397366 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 12091 RingCT/type: yes/0
Extra: 010a0d6da1759965b5569c0e3c4bc65a4ba5d375d170eb95d85f6c68c63d212f90021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f8576d4cd7b6d783a4d195cdca82f17b23ae4bc3337f8ab8fb566f9494f6de93 0.600000000000 1885657 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": 1397376, "vin": [ { "gen": { "height": 1397366 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f8576d4cd7b6d783a4d195cdca82f17b23ae4bc3337f8ab8fb566f9494f6de93" } } ], "extra": [ 1, 10, 13, 109, 161, 117, 153, 101, 181, 86, 156, 14, 60, 75, 198, 90, 75, 165, 211, 117, 209, 112, 235, 149, 216, 95, 108, 104, 198, 61, 33, 47, 144, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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