Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f244c6fbe5fde42b3f77a3309517ff2ca5f0f01a7336350c9339e66f06ad93df

Tx prefix hash: 8c2383f685ae3bea02f00913e71bdf9455da1c667486a6cc37c0e4bdedbc65d5
Tx public key: 77dff341f897afdb27e36a123b05a19d1ff140601d7109ac8c4b78f2534cc95b
Timestamp: 1660435671 Timestamp [UCT]: 2022-08-14 00:07:51 Age [y:d:h:m:s]: 02:137:16:18:09
Block: 565300 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 619825 RingCT/type: yes/0
Extra: 0177dff341f897afdb27e36a123b05a19d1ff140601d7109ac8c4b78f2534cc95b021100000007ec6d1a1a000000000000000000

1 output(s) for total of 8.221035861000 dcy

stealth address amount amount idx
00: 1c8e8951438144911d10c0eca45ecb6c1504a8c6fd13d83019b7584f2d59ebb0 8.221035861000 998184 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": 565310, "vin": [ { "gen": { "height": 565300 } } ], "vout": [ { "amount": 8221035861, "target": { "key": "1c8e8951438144911d10c0eca45ecb6c1504a8c6fd13d83019b7584f2d59ebb0" } } ], "extra": [ 1, 119, 223, 243, 65, 248, 151, 175, 219, 39, 227, 106, 18, 59, 5, 161, 157, 31, 241, 64, 96, 29, 113, 9, 172, 140, 75, 120, 242, 83, 76, 201, 91, 2, 17, 0, 0, 0, 7, 236, 109, 26, 26, 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