Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 57523a830ef3a59beff9609b357086366554fb2bc0ec2d2bb9f9c3c896c63240

Tx prefix hash: 7d704f84176888f321f36e92d3a4b40d1e8a4ca72e39d27aa05e776805322cd7
Tx public key: 783d7a64119538c9e56f349c70214aa97444266acc884d7b5a12b6358435363e
Timestamp: 1669733888 Timestamp [UCT]: 2022-11-29 14:58:08 Age [y:d:h:m:s]: 02:201:17:46:29
Block: 641739 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 665807 RingCT/type: yes/0
Extra: 01783d7a64119538c9e56f349c70214aa97444266acc884d7b5a12b6358435363e021100000001faf35c9c000000000000000000

1 output(s) for total of 4.588305147000 dcy

stealth address amount amount idx
00: 20a1ce2cfa0aa25f027a35b13434d31336334b4f78238bf006570a1a1dc4ec8b 4.588305147000 1081564 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": 641749, "vin": [ { "gen": { "height": 641739 } } ], "vout": [ { "amount": 4588305147, "target": { "key": "20a1ce2cfa0aa25f027a35b13434d31336334b4f78238bf006570a1a1dc4ec8b" } } ], "extra": [ 1, 120, 61, 122, 100, 17, 149, 56, 201, 229, 111, 52, 156, 112, 33, 74, 169, 116, 68, 38, 106, 204, 136, 77, 123, 90, 18, 182, 53, 132, 53, 54, 62, 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