Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a37165f9bae61c165347dc3ff66ebd608a2311fb77dfffa2a00ce3e237e16d97

Tx prefix hash: b48c12b6296abdea0ce1e53999da4888f0aed47e188cfa33ca8338d614c53e34
Tx public key: d44c7bceaa0875812d2b2eeaab29afff7e797a7c0aac11274b6bed8055b27ca9
Timestamp: 1706314405 Timestamp [UCT]: 2024-01-27 00:13:25 Age [y:d:h:m:s]: 01:286:11:09:55
Block: 944063 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 463546 RingCT/type: yes/0
Extra: 01d44c7bceaa0875812d2b2eeaab29afff7e797a7c0aac11274b6bed8055b27ca902110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e1c05e1ced2923b3324aecb5314ccf72f6bd6a5b86a8e5e22e3a2836d9806741 0.600000000000 1402289 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": 944073, "vin": [ { "gen": { "height": 944063 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e1c05e1ced2923b3324aecb5314ccf72f6bd6a5b86a8e5e22e3a2836d9806741" } } ], "extra": [ 1, 212, 76, 123, 206, 170, 8, 117, 129, 45, 43, 46, 234, 171, 41, 175, 255, 126, 121, 122, 124, 10, 172, 17, 39, 75, 107, 237, 128, 85, 178, 124, 169, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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