Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3aed41ce82c8381f7ea5d5f8039d34c541c18ac1f781909e475a2ae941f73752

Tx prefix hash: e94a0a6b07b979470ff76bd4fb85812d50cc928f6845ff23d868af4824e4c79d
Tx public key: ab47d37fe53b8fe6fbe1c9f1ff44c951a062d4a85e2495205741c66075f19a64
Timestamp: 1724118712 Timestamp [UCT]: 2024-08-20 01:51:52 Age [y:d:h:m:s]: 00:227:08:45:40
Block: 1091705 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 162364 RingCT/type: yes/0
Extra: 01ab47d37fe53b8fe6fbe1c9f1ff44c951a062d4a85e2495205741c66075f19a64021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fb4069c056f4fe70bff67ad82a5097e7610544896971aae52a40d498e349438b 0.600000000000 1566338 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": 1091715, "vin": [ { "gen": { "height": 1091705 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fb4069c056f4fe70bff67ad82a5097e7610544896971aae52a40d498e349438b" } } ], "extra": [ 1, 171, 71, 211, 127, 229, 59, 143, 230, 251, 225, 201, 241, 255, 68, 201, 81, 160, 98, 212, 168, 94, 36, 149, 32, 87, 65, 198, 96, 117, 241, 154, 100, 2, 17, 0, 0, 0, 2, 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