Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a4e44dceaca6fd8980a6e7108cd323991ec76201ededc8f6b3ba716865d5aa68

Tx prefix hash: 070c3d913dbdaa4f7831d4c06033d34621554611c08ee232012bdd93eb2ba1fb
Tx public key: 00ad1cef9439778f65a452660fbb3539cef16b75c405e6fa322904efb8427dd5
Timestamp: 1746035341 Timestamp [UCT]: 2025-04-30 17:49:01 Age [y:d:h:m:s]: 00:205:00:01:12
Block: 1272878 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 144226 RingCT/type: yes/0
Extra: 0100ad1cef9439778f65a452660fbb3539cef16b75c405e6fa322904efb8427dd5021100000002d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3df91aef73ca0f1e1cf210b6bfbd241f0c3eb209c28bcff5d3addc826d1aafb7 0.600000000000 1760155 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": 1272888, "vin": [ { "gen": { "height": 1272878 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3df91aef73ca0f1e1cf210b6bfbd241f0c3eb209c28bcff5d3addc826d1aafb7" } } ], "extra": [ 1, 0, 173, 28, 239, 148, 57, 119, 143, 101, 164, 82, 102, 15, 187, 53, 57, 206, 241, 107, 117, 196, 5, 230, 250, 50, 41, 4, 239, 184, 66, 125, 213, 2, 17, 0, 0, 0, 2, 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