Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8c03ad85285952054c2193b47c9778b6e7d83873b00416f754acabeb4f4d9bae

Tx prefix hash: 557e2a0a09eac5498870cfe4eaa4cceabd71b3c58f406f8d855a13a61b68df3e
Tx public key: 7cac1bf0cd04fee7425600bd90218f18b9340fa494b73968b583d36ef50eebfd
Timestamp: 1582435369 Timestamp [UCT]: 2020-02-23 05:22:49 Age [y:d:h:m:s]: 05:256:03:53:59
Block: 70640 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1334053 RingCT/type: yes/0
Extra: 017cac1bf0cd04fee7425600bd90218f18b9340fa494b73968b583d36ef50eebfd02110000000203d36d11000000000000000000

1 output(s) for total of 358.047922927000 dcy

stealth address amount amount idx
00: f5c0cac0713058bc48677a2c447653d628cad6ae0fd7cad34db0436e1fa2a4d3 358.047922927000 130522 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": 70650, "vin": [ { "gen": { "height": 70640 } } ], "vout": [ { "amount": 358047922927, "target": { "key": "f5c0cac0713058bc48677a2c447653d628cad6ae0fd7cad34db0436e1fa2a4d3" } } ], "extra": [ 1, 124, 172, 27, 240, 205, 4, 254, 231, 66, 86, 0, 189, 144, 33, 143, 24, 185, 52, 15, 164, 148, 183, 57, 104, 181, 131, 211, 110, 245, 14, 235, 253, 2, 17, 0, 0, 0, 2, 3, 211, 109, 17, 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