Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ae199fb1dbd0414f7f7ce0dc4f300eb022847cd5596a4545080f4d546d2a04db

Tx prefix hash: 4e2c46fb356550074cb7e6c0701262fcb63d275d1b55809b22976e901c566649
Tx public key: 0f93b47514bbdda54a86e9d6f7c7f03fba9acd483783b1cf555ebdc05c97c3f2
Timestamp: 1749639305 Timestamp [UCT]: 2025-06-11 10:55:05 Age [y:d:h:m:s]: 00:156:13:13:26
Block: 1302709 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109584 RingCT/type: yes/0
Extra: 010f93b47514bbdda54a86e9d6f7c7f03fba9acd483783b1cf555ebdc05c97c3f2021100000001bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 95f643b2f642cf307c68bb5013d29f0bb8d30b5d07a20970c1be04b68859cfef 0.600000000000 1790282 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": 1302719, "vin": [ { "gen": { "height": 1302709 } } ], "vout": [ { "amount": 600000000, "target": { "key": "95f643b2f642cf307c68bb5013d29f0bb8d30b5d07a20970c1be04b68859cfef" } } ], "extra": [ 1, 15, 147, 180, 117, 20, 187, 221, 165, 74, 134, 233, 214, 247, 199, 240, 63, 186, 154, 205, 72, 55, 131, 177, 207, 85, 94, 189, 192, 92, 151, 195, 242, 2, 17, 0, 0, 0, 1, 191, 81, 178, 162, 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