Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e070436c890c5a68fad2ab7126bacd4b6410fa26c2a595ae75963e2e4c3bf57b

Tx prefix hash: 6f3b6cfa108f81d301937081ffdbb1cb2f2ecda1c043b288f56f64bfc572c37b
Tx public key: d010313f333b8aa95eaa936e86ffa23b2010112f38268767933609e715f3df2e
Timestamp: 1745657016 Timestamp [UCT]: 2025-04-26 08:43:36 Age [y:d:h:m:s]: 00:013:18:51:57
Block: 1269752 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 9857 RingCT/type: yes/0
Extra: 01d010313f333b8aa95eaa936e86ffa23b2010112f38268767933609e715f3df2e0211000000056c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b5551222b259fc023096d790c06bc3e307e1c52ab19fb33eaca8a7cec42dc8fd 0.600000000000 1756991 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": 1269762, "vin": [ { "gen": { "height": 1269752 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b5551222b259fc023096d790c06bc3e307e1c52ab19fb33eaca8a7cec42dc8fd" } } ], "extra": [ 1, 208, 16, 49, 63, 51, 59, 138, 169, 94, 170, 147, 110, 134, 255, 162, 59, 32, 16, 17, 47, 56, 38, 135, 103, 147, 54, 9, 231, 21, 243, 223, 46, 2, 17, 0, 0, 0, 5, 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