Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: daec95b0c1a863359539cfe53f1d70a15828414cf5e880b3b7b4d18503b00835

Tx prefix hash: 434a73b335dfc17e1d7d9ddcc544230cd0375230bb2bd880e6679de408d92763
Tx public key: 10f0d5ce263c22d3aa1ad8e0a87eee694336b59836e4673b3cdec2738b53cf8a
Timestamp: 1579188698 Timestamp [UCT]: 2020-01-16 15:31:38 Age [y:d:h:m:s]: 04:315:12:46:37
Block: 46910 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1114965 RingCT/type: yes/0
Extra: 0110f0d5ce263c22d3aa1ad8e0a87eee694336b59836e4673b3cdec2738b53cf8a0211000000034943cd9f000000000000000000

1 output(s) for total of 429.109899981000 dcy

stealth address amount amount idx
00: db25af07a22a3903556056c56841925527d54aa791634e91f7e58883327ce7cc 429.109899981000 86524 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": 46920, "vin": [ { "gen": { "height": 46910 } } ], "vout": [ { "amount": 429109899981, "target": { "key": "db25af07a22a3903556056c56841925527d54aa791634e91f7e58883327ce7cc" } } ], "extra": [ 1, 16, 240, 213, 206, 38, 60, 34, 211, 170, 26, 216, 224, 168, 126, 238, 105, 67, 54, 181, 152, 54, 228, 103, 59, 60, 222, 194, 115, 139, 83, 207, 138, 2, 17, 0, 0, 0, 3, 73, 67, 205, 159, 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