Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf30338523f3651fd621e55f886e8f0e5415e4e4efe3de494370f063c4b8a837

Tx prefix hash: de718cb0a8ae108ec81d95c1183751e387c91828215357042637e6ac74bb840a
Tx public key: 10f637b646b511560a1c525cab7a81b6465a06795f717fb5ed1f052e8ea04154
Timestamp: 1731888562 Timestamp [UCT]: 2024-11-18 00:09:22 Age [y:d:h:m:s]: 00:185:22:46:52
Block: 1156027 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 132758 RingCT/type: yes/0
Extra: 0110f637b646b511560a1c525cab7a81b6465a06795f717fb5ed1f052e8ea04154021100000008007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a97f6953779fa18f14e18fe03f2bd5575485176d8cae6bae6d9973cc800979f3 0.600000000000 1641646 of 15

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": 1156037, "vin": [ { "gen": { "height": 1156027 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a97f6953779fa18f14e18fe03f2bd5575485176d8cae6bae6d9973cc800979f3" } } ], "extra": [ 1, 16, 246, 55, 182, 70, 181, 17, 86, 10, 28, 82, 92, 171, 122, 129, 182, 70, 90, 6, 121, 95, 113, 127, 181, 237, 31, 5, 46, 142, 160, 65, 84, 2, 17, 0, 0, 0, 8, 0, 127, 151, 138, 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