Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 48ed743a555b40aad37474848c94c1e912f4489d8eaa9cc11e195bbcecd8be31

Tx prefix hash: 89dc7d92d0b94fb254b8eb2e79e13d2820dd3fa8c86bcc031ce36b2863e35f22
Tx public key: 5302f276d8c507b3257f3eee066eda03c85ac3bd1bf58ed2e35693f83814f458
Timestamp: 1632369207 Timestamp [UCT]: 2021-09-23 03:53:27 Age [y:d:h:m:s]: 03:044:17:25:13
Block: 339205 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 808134 RingCT/type: yes/0
Extra: 015302f276d8c507b3257f3eee066eda03c85ac3bd1bf58ed2e35693f83814f4580211000000168d0de867000000000000000000

1 output(s) for total of 46.139560953000 dcy

stealth address amount amount idx
00: e1e1a777f10db05193df6e4ff5b553e08c153fee1ef05552c48d8e6d52321586 46.139560953000 697730 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": 339215, "vin": [ { "gen": { "height": 339205 } } ], "vout": [ { "amount": 46139560953, "target": { "key": "e1e1a777f10db05193df6e4ff5b553e08c153fee1ef05552c48d8e6d52321586" } } ], "extra": [ 1, 83, 2, 242, 118, 216, 197, 7, 179, 37, 127, 62, 238, 6, 110, 218, 3, 200, 90, 195, 189, 27, 245, 142, 210, 227, 86, 147, 248, 56, 20, 244, 88, 2, 17, 0, 0, 0, 22, 141, 13, 232, 103, 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