Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 713c25ebf866f5b0d8ab319defa7fd819930062e619799fa514ce0abfc7efac2

Tx prefix hash: df075c46c2738f1ca48f42cc38a64c8285da71d55206bb87a3d54751d1c6e2f6
Tx public key: fce7d56276c5154490f81f404e4787312f4ca286249acd25b0dcaacd54e17e6e
Timestamp: 1737330977 Timestamp [UCT]: 2025-01-19 23:56:17 Age [y:d:h:m:s]: 00:149:12:31:51
Block: 1201039 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106618 RingCT/type: yes/0
Extra: 01fce7d56276c5154490f81f404e4787312f4ca286249acd25b0dcaacd54e17e6e021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ad2311cd9b46cdbe68232034d19cb8ee97f2a3a78cb43c0128398435ac6b7b67 0.600000000000 1687686 of 15

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": 1201049, "vin": [ { "gen": { "height": 1201039 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ad2311cd9b46cdbe68232034d19cb8ee97f2a3a78cb43c0128398435ac6b7b67" } } ], "extra": [ 1, 252, 231, 213, 98, 118, 197, 21, 68, 144, 248, 31, 64, 78, 71, 135, 49, 47, 76, 162, 134, 36, 154, 205, 37, 176, 220, 170, 205, 84, 225, 126, 110, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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