Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e85e42aab5df07ccf962718e2c3356c23283d7aee6622f044b8566535571ff50

Tx prefix hash: 56675f6265769621ad489d7e0f32db66d7fe6fdfe356e35b400a75fdb2a61f88
Tx public key: a771b818a07d6b1f3c7ecf18252dfb5b8ef1756e1760e4d6ef3b67fcb5a1f529
Timestamp: 1626769841 Timestamp [UCT]: 2021-07-20 08:30:41 Age [y:d:h:m:s]: 03:171:03:42:45
Block: 297467 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 893982 RingCT/type: yes/0
Extra: 01a771b818a07d6b1f3c7ecf18252dfb5b8ef1756e1760e4d6ef3b67fcb5a1f52902110000004a04712537000000000000000000

1 output(s) for total of 63.440827448000 dcy

stealth address amount amount idx
00: fe77fae1f19e602bd928f395a7c9bbebddfb4b8e2486759519f055d0ea5d60f9 63.440827448000 622573 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": 297477, "vin": [ { "gen": { "height": 297467 } } ], "vout": [ { "amount": 63440827448, "target": { "key": "fe77fae1f19e602bd928f395a7c9bbebddfb4b8e2486759519f055d0ea5d60f9" } } ], "extra": [ 1, 167, 113, 184, 24, 160, 125, 107, 31, 60, 126, 207, 24, 37, 45, 251, 91, 142, 241, 117, 110, 23, 96, 228, 214, 239, 59, 103, 252, 181, 161, 245, 41, 2, 17, 0, 0, 0, 74, 4, 113, 37, 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