Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 44c0c6fa6bd2aab6c2a64ed6840a22ec99057821019015754b1757af61db74e4

Tx prefix hash: dc62c8ea5fd1207dd518e5a01c51b24e6e0e563b8773ff1c4dd7d0e09814a039
Tx public key: dd44b92ad081f7fb511ee2b95d8dd422d58801eeb9acf9a596acb87e6f396439
Timestamp: 1662137192 Timestamp [UCT]: 2022-09-02 16:46:32 Age [y:d:h:m:s]: 02:059:04:45:14
Block: 579344 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 563725 RingCT/type: yes/0
Extra: 01dd44b92ad081f7fb511ee2b95d8dd422d58801eeb9acf9a596acb87e6f39643902110000000275e3f0e9000000000000000000

1 output(s) for total of 7.385721378000 dcy

stealth address amount amount idx
00: 830d84ead35e9ecdc377bd6da367937a9701f4783e9dd18fb744c92724307f99 7.385721378000 1012800 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": 579354, "vin": [ { "gen": { "height": 579344 } } ], "vout": [ { "amount": 7385721378, "target": { "key": "830d84ead35e9ecdc377bd6da367937a9701f4783e9dd18fb744c92724307f99" } } ], "extra": [ 1, 221, 68, 185, 42, 208, 129, 247, 251, 81, 30, 226, 185, 93, 141, 212, 34, 213, 136, 1, 238, 185, 172, 249, 165, 150, 172, 184, 126, 111, 57, 100, 57, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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