Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 95fac647a3cb8f815006633be17fa704c733190b84afe7737da81e5b43d9c8fc

Tx prefix hash: 9228cb85e51145f253907021ef935b68e2bcb64f4df9f3e1c414f1607b5b65a3
Tx public key: a37dad0a806240ab9a5ddae4854bd099d17927745a9be7a64fa40ece601f4b98
Timestamp: 1629976455 Timestamp [UCT]: 2021-08-26 11:14:15 Age [y:d:h:m:s]: 04:066:17:48:35
Block: 321123 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1080588 RingCT/type: yes/0
Extra: 01a37dad0a806240ab9a5ddae4854bd099d17927745a9be7a64fa40ece601f4b980211000000590254cd56000000000000000000

1 output(s) for total of 52.964716992000 dcy

stealth address amount amount idx
00: b40b81995db74e64c45b78f6b3327d23b02fcc2c2c6e48bf8c69f9a896d6f682 52.964716992000 666744 of 0

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": 321133, "vin": [ { "gen": { "height": 321123 } } ], "vout": [ { "amount": 52964716992, "target": { "key": "b40b81995db74e64c45b78f6b3327d23b02fcc2c2c6e48bf8c69f9a896d6f682" } } ], "extra": [ 1, 163, 125, 173, 10, 128, 98, 64, 171, 154, 93, 218, 228, 133, 75, 208, 153, 209, 121, 39, 116, 90, 155, 231, 166, 79, 164, 14, 206, 96, 31, 75, 152, 2, 17, 0, 0, 0, 89, 2, 84, 205, 86, 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