Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 785d9c6a986c5341829500897c484eb2cda5b0dde87858a6883b1e93f49ff708

Tx prefix hash: 352315433cce3c443245fe6cfd3966ee2743a71d72e2e19cfcd09e6683b7c428
Tx public key: 2a1504b7d7c5668bbf333ef973a76a879fcc1d8ea918174a0d1288a5feb3b544
Timestamp: 1704568180 Timestamp [UCT]: 2024-01-06 19:09:40 Age [y:d:h:m:s]: 00:313:08:29:28
Block: 929600 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 224377 RingCT/type: yes/0
Extra: 012a1504b7d7c5668bbf333ef973a76a879fcc1d8ea918174a0d1288a5feb3b54402110000000b7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9aa8039a6c8b0f48e0b2fe6ff4ef7df8af57af7cb304a120dce2372849999b5d 0.600000000000 1387476 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": 929610, "vin": [ { "gen": { "height": 929600 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9aa8039a6c8b0f48e0b2fe6ff4ef7df8af57af7cb304a120dce2372849999b5d" } } ], "extra": [ 1, 42, 21, 4, 183, 215, 197, 102, 139, 191, 51, 62, 249, 115, 167, 106, 135, 159, 204, 29, 142, 169, 24, 23, 74, 13, 18, 136, 165, 254, 179, 181, 68, 2, 17, 0, 0, 0, 11, 122, 156, 244, 199, 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