Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ed8f9164278fe640555c4844f80dca72f483d0df9eae83b4b7f2ecc8f30df0b

Tx prefix hash: cb615f3d0c788d86768abdf8551bb9b2cbae1e4ef89f979d8d59414615288daf
Tx public key: 79345362c487904a406de581efd772221f51dc38f7e5120019f0e77d944a18cb
Timestamp: 1733122116 Timestamp [UCT]: 2024-12-02 06:48:36 Age [y:d:h:m:s]: 00:341:20:01:07
Block: 1166247 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 241825 RingCT/type: yes/0
Extra: 0179345362c487904a406de581efd772221f51dc38f7e5120019f0e77d944a18cb021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a3d49bb3268ae32206dea162e8efdf80bbc81cb9f37d7bf4272014729756a98b 0.600000000000 1651924 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": 1166257, "vin": [ { "gen": { "height": 1166247 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a3d49bb3268ae32206dea162e8efdf80bbc81cb9f37d7bf4272014729756a98b" } } ], "extra": [ 1, 121, 52, 83, 98, 196, 135, 144, 74, 64, 109, 229, 129, 239, 215, 114, 34, 31, 81, 220, 56, 247, 229, 18, 0, 25, 240, 231, 125, 148, 74, 24, 203, 2, 17, 0, 0, 0, 5, 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