Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 363abc61686a0ae0357c280b529eb4510c77a25c8cfcd9921a1f4b7a2e31b108

Tx prefix hash: b13467ce93a1cb17efefa972d8e2aa54cd03cc488c379ba74769f69307d92efd
Tx public key: c3e8f18433d0ff47d4e9c243c18f4f26ba6064c95e343c565baf98c2fe4765f9
Timestamp: 1581861142 Timestamp [UCT]: 2020-02-16 13:52:22 Age [y:d:h:m:s]: 04:321:02:52:23
Block: 66243 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1121756 RingCT/type: yes/0
Extra: 01c3e8f18433d0ff47d4e9c243c18f4f26ba6064c95e343c565baf98c2fe4765f9021100000006d81c26c0000000000000000000

1 output(s) for total of 370.262945256000 dcy

stealth address amount amount idx
00: b86fab225892ef0c3e2ea4f977fb02176615bdf7862eb67e7a6dd7c4b2ac9963 370.262945256000 122024 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": 66253, "vin": [ { "gen": { "height": 66243 } } ], "vout": [ { "amount": 370262945256, "target": { "key": "b86fab225892ef0c3e2ea4f977fb02176615bdf7862eb67e7a6dd7c4b2ac9963" } } ], "extra": [ 1, 195, 232, 241, 132, 51, 208, 255, 71, 212, 233, 194, 67, 193, 143, 79, 38, 186, 96, 100, 201, 94, 52, 60, 86, 91, 175, 152, 194, 254, 71, 101, 249, 2, 17, 0, 0, 0, 6, 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