Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 759bc14e96e27d5a77f0c24bc83002e921e559436e5ef603a587e9c23185c40f

Tx prefix hash: 08b200385acc5667e5c41edcfcead8293f5525ac5abf3231a9a2a15ccf625b85
Tx public key: af11b244cf9ebd1e7f6e3b10b700fca6138dc438d91efa35f578cf0a7ddc2b65
Timestamp: 1707233155 Timestamp [UCT]: 2024-02-06 15:25:55 Age [y:d:h:m:s]: 01:090:18:35:58
Block: 951701 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 325954 RingCT/type: yes/0
Extra: 01af11b244cf9ebd1e7f6e3b10b700fca6138dc438d91efa35f578cf0a7ddc2b6502110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cdcb10a220e56c597e7875ffa32c904bd8479b13386227f7079c32e1a167f3c8 0.600000000000 1410505 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": 951711, "vin": [ { "gen": { "height": 951701 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cdcb10a220e56c597e7875ffa32c904bd8479b13386227f7079c32e1a167f3c8" } } ], "extra": [ 1, 175, 17, 178, 68, 207, 158, 189, 30, 127, 110, 59, 16, 183, 0, 252, 166, 19, 141, 196, 56, 217, 30, 250, 53, 245, 120, 207, 10, 125, 220, 43, 101, 2, 17, 0, 0, 0, 3, 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