Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e04170cfc03f4109691a3d1d1d1d77ece30ae8aecad65fa8e6b5f54e3b0ff40f

Tx prefix hash: 931beb4a78724b59057080d2509a79bbf530802c89e70ec9be5569be6160b0e6
Tx public key: 567f9cd1d0432a9fed4e665c070c13be5c37cf96c877de2b8ce63478805159e7
Timestamp: 1584923967 Timestamp [UCT]: 2020-03-23 00:39:27 Age [y:d:h:m:s]: 04:343:19:13:04
Block: 87046 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1142259 RingCT/type: yes/0
Extra: 01567f9cd1d0432a9fed4e665c070c13be5c37cf96c877de2b8ce63478805159e7021100000024e5e30634000000000000000000

1 output(s) for total of 315.923001679000 dcy

stealth address amount amount idx
00: 91c75fe18edfa55c8ab3d888f3fec4dfb08a2800dc11fca33af39d483b5957f8 315.923001679000 156940 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": 87056, "vin": [ { "gen": { "height": 87046 } } ], "vout": [ { "amount": 315923001679, "target": { "key": "91c75fe18edfa55c8ab3d888f3fec4dfb08a2800dc11fca33af39d483b5957f8" } } ], "extra": [ 1, 86, 127, 156, 209, 208, 67, 42, 159, 237, 78, 102, 92, 7, 12, 19, 190, 92, 55, 207, 150, 200, 119, 222, 43, 140, 230, 52, 120, 128, 81, 89, 231, 2, 17, 0, 0, 0, 36, 229, 227, 6, 52, 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