Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9ce4401430014ee42ce6c310f51a601821e1dadc1a4a331301307cde16fd72ed

Tx prefix hash: 18ed874041a0e70fe6df26bf8951fb1b4a9db61e4d58af99087cb94b7bcf4069
Tx public key: 7efa06d628eea5e8a3e7e9687abdfbc3f247750bc41b1ec8fc5cd09d87782ca8
Timestamp: 1656311928 Timestamp [UCT]: 2022-06-27 06:38:48 Age [y:d:h:m:s]: 02:297:01:46:53
Block: 531304 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 733431 RingCT/type: yes/0
Extra: 017efa06d628eea5e8a3e7e9687abdfbc3f247750bc41b1ec8fc5cd09d87782ca8021100000001c9067537000000000000000000

1 output(s) for total of 10.655392523000 dcy

stealth address amount amount idx
00: 808d7700d9ebc22da3ae812dc73dddaa6b1d767074c717136f006f77f00eee11 10.655392523000 960433 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": 531314, "vin": [ { "gen": { "height": 531304 } } ], "vout": [ { "amount": 10655392523, "target": { "key": "808d7700d9ebc22da3ae812dc73dddaa6b1d767074c717136f006f77f00eee11" } } ], "extra": [ 1, 126, 250, 6, 214, 40, 238, 165, 232, 163, 231, 233, 104, 122, 189, 251, 195, 242, 71, 117, 11, 196, 27, 30, 200, 252, 92, 208, 157, 135, 120, 44, 168, 2, 17, 0, 0, 0, 1, 201, 6, 117, 55, 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