Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ae3eda4298d295b20fb745b0e3fcbdfeedf6e0bca062e973521d120a80c3ead9

Tx prefix hash: 9f6d75063359800c98a5b5c3d912678157c514f9472e1d23a0051736300206c1
Tx public key: e4ac44aee4109f5a8b40e2c1261997cb2c44ec3b6a25a37aadd41e75a8a76da1
Timestamp: 1745447174 Timestamp [UCT]: 2025-04-23 22:26:14 Age [y:d:h:m:s]: 00:211:19:23:59
Block: 1268001 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 149103 RingCT/type: yes/0
Extra: 01e4ac44aee4109f5a8b40e2c1261997cb2c44ec3b6a25a37aadd41e75a8a76da102110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a714e13707d50ce807b834fc90b8f521b49347efc28510f7bc895a31286209c7 0.600000000000 1755230 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": 1268011, "vin": [ { "gen": { "height": 1268001 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a714e13707d50ce807b834fc90b8f521b49347efc28510f7bc895a31286209c7" } } ], "extra": [ 1, 228, 172, 68, 174, 228, 16, 159, 90, 139, 64, 226, 193, 38, 25, 151, 203, 44, 68, 236, 59, 106, 37, 163, 122, 173, 212, 30, 117, 168, 167, 109, 161, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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