Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fcd2a23f5eba00241b3034870444d53c31bac02e682c47c81b2094bc00dfc670

Tx prefix hash: 1ba9c3b1f8c829901e92ad115e0fe43c6f33ac93b266bf5fedefb684709c9447
Tx public key: e2c841b6a7fd985a06fc38bb2de28360945b4a8779f7f15a41259f5ceeb11656
Timestamp: 1700741508 Timestamp [UCT]: 2023-11-23 12:11:48 Age [y:d:h:m:s]: 01:172:08:42:26
Block: 897894 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 384385 RingCT/type: yes/0
Extra: 01e2c841b6a7fd985a06fc38bb2de28360945b4a8779f7f15a41259f5ceeb1165602110000000375e3f0e9000000000000000000

1 output(s) for total of 0.649986641000 dcy

stealth address amount amount idx
00: a95357e4658518d8e37f45c13ffdef3db472710086a374cd0c38e7f36d6e2232 0.649986641000 1354291 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": 897904, "vin": [ { "gen": { "height": 897894 } } ], "vout": [ { "amount": 649986641, "target": { "key": "a95357e4658518d8e37f45c13ffdef3db472710086a374cd0c38e7f36d6e2232" } } ], "extra": [ 1, 226, 200, 65, 182, 167, 253, 152, 90, 6, 252, 56, 187, 45, 226, 131, 96, 148, 91, 74, 135, 121, 247, 241, 90, 65, 37, 159, 92, 238, 177, 22, 86, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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