Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ca0467f0fa00f1903748ec5335e8426ba71f31653f6f6dfc9238db00715c989e

Tx prefix hash: b103a6230c01c70e87a06201b25528b6f228a1fcc1ad5536291de5042673e6a0
Tx public key: e719ce7485b69c5bf5cafbe89b8860e257fb7891f36073793bf906008b251e9a
Timestamp: 1578934182 Timestamp [UCT]: 2020-01-13 16:49:42 Age [y:d:h:m:s]: 04:351:09:46:36
Block: 44816 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1140619 RingCT/type: yes/0
Extra: 01e719ce7485b69c5bf5cafbe89b8860e257fb7891f36073793bf906008b251e9a0211000000114943cd9f000000000000000000

1 output(s) for total of 436.084709655000 dcy

stealth address amount amount idx
00: b085daff12f4cdbcd1223bcb3fc4c405a564e78cc0c3a2522f025f2596d719e7 436.084709655000 81662 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": 44826, "vin": [ { "gen": { "height": 44816 } } ], "vout": [ { "amount": 436084709655, "target": { "key": "b085daff12f4cdbcd1223bcb3fc4c405a564e78cc0c3a2522f025f2596d719e7" } } ], "extra": [ 1, 231, 25, 206, 116, 133, 182, 156, 91, 245, 202, 251, 232, 155, 136, 96, 226, 87, 251, 120, 145, 243, 96, 115, 121, 59, 249, 6, 0, 139, 37, 30, 154, 2, 17, 0, 0, 0, 17, 73, 67, 205, 159, 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