Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 98b3b4c132a529fb16462e6deb8ad2ab3add5a4470f6571da3299d3c0def1667

Tx prefix hash: c97d259ef09756d71d8b31da1f651c69542b13461bb09ec3cc5650859991fa5a
Tx public key: c9ecc88ca1dec0a0ea89da7b282cc16fb57cd14ed4a414be01003b408fe5558e
Timestamp: 1733872035 Timestamp [UCT]: 2024-12-10 23:07:15 Age [y:d:h:m:s]: 00:144:08:50:02
Block: 1172465 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102986 RingCT/type: yes/0
Extra: 01c9ecc88ca1dec0a0ea89da7b282cc16fb57cd14ed4a414be01003b408fe5558e021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 058e8618b69fe5e6b711aac0c3d8fd321985320ab3b9e9ea7ceef83ad9b2d7be 0.600000000000 1658358 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": 1172475, "vin": [ { "gen": { "height": 1172465 } } ], "vout": [ { "amount": 600000000, "target": { "key": "058e8618b69fe5e6b711aac0c3d8fd321985320ab3b9e9ea7ceef83ad9b2d7be" } } ], "extra": [ 1, 201, 236, 200, 140, 161, 222, 192, 160, 234, 137, 218, 123, 40, 44, 193, 111, 181, 124, 209, 78, 212, 164, 20, 190, 1, 0, 59, 64, 143, 229, 85, 142, 2, 17, 0, 0, 0, 1, 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