Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8c056d5c01c2c44cf9ecac5f34c7704a46bade940fdac7a8b0a28049a331bb42

Tx prefix hash: 4fea1d86a2203bfc60b266ca9c0272b590888811ba032335020c06e8cf44f729
Tx public key: fd925fde9c99bd21840123bd14da15c2046e50b4cc10500c6ed22b03736bc39b
Timestamp: 1721667260 Timestamp [UCT]: 2024-07-22 16:54:20 Age [y:d:h:m:s]: 00:246:14:26:46
Block: 1071364 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 176158 RingCT/type: yes/0
Extra: 01fd925fde9c99bd21840123bd14da15c2046e50b4cc10500c6ed22b03736bc39b021100000005e914dd15000000000000000000

1 output(s) for total of 0.615600000000 dcy

stealth address amount amount idx
00: 7f4892a069421ff6bbcc734ef4cefbd1f2b363d53c6d5c0f4dc4fe21a5814edc 0.615600000000 1543563 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": 1071374, "vin": [ { "gen": { "height": 1071364 } } ], "vout": [ { "amount": 615600000, "target": { "key": "7f4892a069421ff6bbcc734ef4cefbd1f2b363d53c6d5c0f4dc4fe21a5814edc" } } ], "extra": [ 1, 253, 146, 95, 222, 156, 153, 189, 33, 132, 1, 35, 189, 20, 218, 21, 194, 4, 110, 80, 180, 204, 16, 80, 12, 110, 210, 43, 3, 115, 107, 195, 155, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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