Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db9c2c4d2bafa298a4883a770e7364ef484e4fee34753fddba9442dd0b976ae4

Tx prefix hash: 8109487c5202f98f55b9fddff5c72db2f6c9469c32ed8a30f5447e89abd4f3d2
Tx public key: 4a84f93aeb710d3fcf7fd0d8075713784612702ff6d6adb339a675035071b167
Timestamp: 1581901300 Timestamp [UCT]: 2020-02-17 01:01:40 Age [y:d:h:m:s]: 04:320:14:10:51
Block: 66340 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1121616 RingCT/type: yes/0
Extra: 014a84f93aeb710d3fcf7fd0d8075713784612702ff6d6adb339a675035071b1670211000000068a2ee0d9000000000000000000

1 output(s) for total of 369.989032016000 dcy

stealth address amount amount idx
00: 4ce0f87df89e279944d6f842312436755b84e4f167e55892fde550a894ae837d 369.989032016000 122245 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": 66350, "vin": [ { "gen": { "height": 66340 } } ], "vout": [ { "amount": 369989032016, "target": { "key": "4ce0f87df89e279944d6f842312436755b84e4f167e55892fde550a894ae837d" } } ], "extra": [ 1, 74, 132, 249, 58, 235, 113, 13, 63, 207, 127, 208, 216, 7, 87, 19, 120, 70, 18, 112, 47, 246, 214, 173, 179, 57, 166, 117, 3, 80, 113, 177, 103, 2, 17, 0, 0, 0, 6, 138, 46, 224, 217, 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