Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 835eaceb0c289178f309daefe3703ff615d594e518ebf8a4ce5ed35b3ac9526f

Tx prefix hash: 8e071d4ac8644005005ba7acb5c1546e3258c2cb7ad62c804990aa5666b667e8
Tx public key: e3d4cd2b3ff0baa97c745d09aed01578950443ffbc071eeaa55dc02a67fa45ea
Timestamp: 1577929163 Timestamp [UCT]: 2020-01-02 01:39:23 Age [y:d:h:m:s]: 05:303:14:30:47
Block: 36804 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1364511 RingCT/type: yes/0
Extra: 01e3d4cd2b3ff0baa97c745d09aed01578950443ffbc071eeaa55dc02a67fa45ea021100000010d81c26c0000000000000000000

1 output(s) for total of 463.604505141000 dcy

stealth address amount amount idx
00: e0fd3736503366857b3e34d51e3dc2aa7924b7af3aed8d07df77e2101c24c443 463.604505141000 62386 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": 36814, "vin": [ { "gen": { "height": 36804 } } ], "vout": [ { "amount": 463604505141, "target": { "key": "e0fd3736503366857b3e34d51e3dc2aa7924b7af3aed8d07df77e2101c24c443" } } ], "extra": [ 1, 227, 212, 205, 43, 63, 240, 186, 169, 124, 116, 93, 9, 174, 208, 21, 120, 149, 4, 67, 255, 188, 7, 30, 234, 165, 93, 192, 42, 103, 250, 69, 234, 2, 17, 0, 0, 0, 16, 216, 28, 38, 192, 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