Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9627c84006aaf8c9e6913b67e075f48cefa9403cca5704d2cc21f0d595e05d7c

Tx prefix hash: c8e180c9c442308543c12c6e63dfaac70b7e5c0e90c47905d7a7ecc9989ad678
Tx public key: 7d0215f1d32f30d735466acd879b4e446a7f82538030b895b2092e1ca4d6fe5d
Timestamp: 1583019556 Timestamp [UCT]: 2020-02-29 23:39:16 Age [y:d:h:m:s]: 05:071:10:19:01
Block: 74394 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1205403 RingCT/type: yes/0
Extra: 017d0215f1d32f30d735466acd879b4e446a7f82538030b895b2092e1ca4d6fe5d0211000000e0c71d3ff9000000000000000000

1 output(s) for total of 347.944605640000 dcy

stealth address amount amount idx
00: e8b965bd542cb55f2cc23a46d994ce4c5e9689acd2b18fe4f7d1676e5d64d8a1 347.944605640000 137671 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": 74404, "vin": [ { "gen": { "height": 74394 } } ], "vout": [ { "amount": 347944605640, "target": { "key": "e8b965bd542cb55f2cc23a46d994ce4c5e9689acd2b18fe4f7d1676e5d64d8a1" } } ], "extra": [ 1, 125, 2, 21, 241, 211, 47, 48, 215, 53, 70, 106, 205, 135, 155, 78, 68, 106, 127, 130, 83, 128, 48, 184, 149, 178, 9, 46, 28, 164, 214, 254, 93, 2, 17, 0, 0, 0, 224, 199, 29, 63, 249, 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