Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eecc6ec09414e47b1add6da2a7daddb37b27d3ff028ed340bbae86d310c0f1ca

Tx prefix hash: e499936557406ad0aae41c849ba114cd20ada747d4ec853ed6bcd67bb5e9cc91
Tx public key: f6f5e108b605a37e1f0f3627098125984ac593f9d463b8ddad01bb7dad65c0ac
Timestamp: 1684880128 Timestamp [UCT]: 2023-05-23 22:15:28 Age [y:d:h:m:s]: 01:193:00:43:07
Block: 766638 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 399376 RingCT/type: yes/0
Extra: 01f6f5e108b605a37e1f0f3627098125984ac593f9d463b8ddad01bb7dad65c0ac021100000001faf35c9c000000000000000000

1 output(s) for total of 1.769335691000 dcy

stealth address amount amount idx
00: 2fd3b89a0bc10c74930a8d2f5b7e01346512d65eae700bb605f33d0c58ea15d3 1.769335691000 1215693 of 0

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": 766648, "vin": [ { "gen": { "height": 766638 } } ], "vout": [ { "amount": 1769335691, "target": { "key": "2fd3b89a0bc10c74930a8d2f5b7e01346512d65eae700bb605f33d0c58ea15d3" } } ], "extra": [ 1, 246, 245, 225, 8, 182, 5, 163, 126, 31, 15, 54, 39, 9, 129, 37, 152, 74, 197, 147, 249, 212, 99, 184, 221, 173, 1, 187, 125, 173, 101, 192, 172, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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