Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a556e929adb4eeda1341507a7608502e53d50ec53ad6b9b509c001de93db9959

Tx prefix hash: 4569fe4aab0c6180af0f228dd7c19cc611a6ea64896ec0a6ae2785218304f2c6
Tx public key: d64c81d302b6a1f1c962c0885aa265bc748d7d77341f729d7dacb5da2235f295
Timestamp: 1629979195 Timestamp [UCT]: 2021-08-26 11:59:55 Age [y:d:h:m:s]: 03:181:09:01:35
Block: 321136 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 903903 RingCT/type: yes/0
Extra: 01d64c81d302b6a1f1c962c0885aa265bc748d7d77341f729d7dacb5da2235f2950211000000034a0f5013000000000000000000

1 output(s) for total of 52.959464079000 dcy

stealth address amount amount idx
00: de7a2f1fdb80da52b1b7857bd0d28a0c48ce69e43c90b69e0642450db5f66510 52.959464079000 666771 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": 321146, "vin": [ { "gen": { "height": 321136 } } ], "vout": [ { "amount": 52959464079, "target": { "key": "de7a2f1fdb80da52b1b7857bd0d28a0c48ce69e43c90b69e0642450db5f66510" } } ], "extra": [ 1, 214, 76, 129, 211, 2, 182, 161, 241, 201, 98, 192, 136, 90, 162, 101, 188, 116, 141, 125, 119, 52, 31, 114, 157, 125, 172, 181, 218, 34, 53, 242, 149, 2, 17, 0, 0, 0, 3, 74, 15, 80, 19, 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