Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0c1f94995f5cecb8b71955bcd96c0e70a53abf5f0617356dd818eda3f932a23e

Tx prefix hash: ec60287c57f4b32e1a55becabf8d7457593dd628a6eef0f9f0b9d66f8cbcff88
Tx public key: 58ea6a93a80a96144de2d29929595ab556bc7cb01c298f89cebf1ae88a2dc5e0
Timestamp: 1671174237 Timestamp [UCT]: 2022-12-16 07:03:57 Age [y:d:h:m:s]: 02:160:00:50:49
Block: 653659 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 636101 RingCT/type: yes/0
Extra: 0158ea6a93a80a96144de2d29929595ab556bc7cb01c298f89cebf1ae88a2dc5e00211000000017e406890000000000000000000

1 output(s) for total of 4.189443786000 dcy

stealth address amount amount idx
00: 896a3f54a154e427f1a8db1be61a75b15aa4c5d2dc3c8becc51500f01e0457b5 4.189443786000 1094128 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": 653669, "vin": [ { "gen": { "height": 653659 } } ], "vout": [ { "amount": 4189443786, "target": { "key": "896a3f54a154e427f1a8db1be61a75b15aa4c5d2dc3c8becc51500f01e0457b5" } } ], "extra": [ 1, 88, 234, 106, 147, 168, 10, 150, 20, 77, 226, 210, 153, 41, 89, 90, 181, 86, 188, 124, 176, 28, 41, 143, 137, 206, 191, 26, 232, 138, 45, 197, 224, 2, 17, 0, 0, 0, 1, 126, 64, 104, 144, 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