Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0b89604da73ec35f1c0cdb3d6c75921a39cbea40a277494ef0bdc2bef9090a37

Tx prefix hash: 6753b65d726bdddc49f462582388058b5fa19ad98f303d9afde584b9a86aea3d
Tx public key: 8c56e73ccabacaaa65beea544bf31fbf01ac6922e9c156fffad79a6ec2e9f746
Timestamp: 1727759687 Timestamp [UCT]: 2024-10-01 05:14:47 Age [y:d:h:m:s]: 00:054:08:57:10
Block: 1121888 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 38850 RingCT/type: yes/0
Extra: 018c56e73ccabacaaa65beea544bf31fbf01ac6922e9c156fffad79a6ec2e9f746021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e0a05591f9fb58e9aa668319d6d3e15b88f063a492ce7ef14255a47dc35a76c8 0.600000000000 1604245 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": 1121898, "vin": [ { "gen": { "height": 1121888 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e0a05591f9fb58e9aa668319d6d3e15b88f063a492ce7ef14255a47dc35a76c8" } } ], "extra": [ 1, 140, 86, 231, 60, 202, 186, 202, 170, 101, 190, 234, 84, 75, 243, 31, 191, 1, 172, 105, 34, 233, 193, 86, 255, 250, 215, 154, 110, 194, 233, 247, 70, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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