Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1d5ebfa084401e1c029fafd89bf20c0a9e59fd029a0131fddde95a488962a1f8

Tx prefix hash: a1669d3c2fb5f02c5e3ba5beb4709e5e3ac70cc635c4f9e7a7e0c36b7543a163
Tx public key: 0f85cb0e1c6c42ebb0bc4a2bef6f15ccb601589c1f9f10d9225a8e910e7fa673
Timestamp: 1720391450 Timestamp [UCT]: 2024-07-07 22:30:50 Age [y:d:h:m:s]: 00:274:14:59:01
Block: 1060802 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 196202 RingCT/type: yes/0
Extra: 010f85cb0e1c6c42ebb0bc4a2bef6f15ccb601589c1f9f10d9225a8e910e7fa67302110000000891e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bd4289618060c22090b6d206813ba31ebbbf36d8c37ef9a6bbc81a99676dac30 0.600000000000 1531289 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": 1060812, "vin": [ { "gen": { "height": 1060802 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bd4289618060c22090b6d206813ba31ebbbf36d8c37ef9a6bbc81a99676dac30" } } ], "extra": [ 1, 15, 133, 203, 14, 28, 108, 66, 235, 176, 188, 74, 43, 239, 111, 21, 204, 182, 1, 88, 156, 31, 159, 16, 217, 34, 90, 142, 145, 14, 127, 166, 115, 2, 17, 0, 0, 0, 8, 145, 225, 60, 4, 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