Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec63d6a8d4667252ff3058f723a6fb1f9703c847db6bd233f9af314dd0bd06fa

Tx prefix hash: ab6071c73993ed55d60c83e9d3176e7784bbb518e076476a50c1e789b5944537
Tx public key: f29cba6455c246eaa8b794bf940177da7973634976c2c0efba8c6b88c2b982b4
Timestamp: 1739120881 Timestamp [UCT]: 2025-02-09 17:08:01 Age [y:d:h:m:s]: 00:285:07:13:59
Block: 1215648 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 201659 RingCT/type: yes/0
Extra: 01f29cba6455c246eaa8b794bf940177da7973634976c2c0efba8c6b88c2b982b40211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e2fb4ae94a6e4e2d7a09a456ea6e54de32491cad06c60014185f4fa5f176caa7 0.600000000000 1702447 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": 1215658, "vin": [ { "gen": { "height": 1215648 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e2fb4ae94a6e4e2d7a09a456ea6e54de32491cad06c60014185f4fa5f176caa7" } } ], "extra": [ 1, 242, 156, 186, 100, 85, 194, 70, 234, 168, 183, 148, 191, 148, 1, 119, 218, 121, 115, 99, 73, 118, 194, 192, 239, 186, 140, 107, 136, 194, 185, 130, 180, 2, 17, 0, 0, 0, 6, 31, 10, 83, 235, 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