Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d274322c44de0f7a75e30892c589e9d77aabbd92f9eb8c1762fe23d9b5130634

Tx prefix hash: c4ed5c4b86ebff20961f4e6ab873ac696c7de9c3bab76b5460a692a9d2f6ac60
Tx public key: 598168fdf9ffc49f3ad862502e264cd773019081a9e6dc79db671361f49fae33
Timestamp: 1723609934 Timestamp [UCT]: 2024-08-14 04:32:14 Age [y:d:h:m:s]: 00:235:23:27:32
Block: 1087484 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 168514 RingCT/type: yes/0
Extra: 01598168fdf9ffc49f3ad862502e264cd773019081a9e6dc79db671361f49fae33021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d5ef4831e4fc722576e55b631712cb56b2f3a6b080149b1cd8c23743669ca05f 0.600000000000 1562093 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": 1087494, "vin": [ { "gen": { "height": 1087484 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d5ef4831e4fc722576e55b631712cb56b2f3a6b080149b1cd8c23743669ca05f" } } ], "extra": [ 1, 89, 129, 104, 253, 249, 255, 196, 159, 58, 216, 98, 80, 46, 38, 76, 215, 115, 1, 144, 129, 169, 230, 220, 121, 219, 103, 19, 97, 244, 159, 174, 51, 2, 17, 0, 0, 0, 4, 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