Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4f791b6e42f491a414af771698266f6c9fa6dc8e9779a27c14646d3d0e60ccad

Tx prefix hash: 63623ff3573ad41fda13ecda54e81d49d636fddbf18cb2e16cc30b9ac1ed7665
Tx public key: 34c2eb65e5bcef1608978cf4a3b428e453e452f0f7ac5e6d7a258a387b666e6b
Timestamp: 1722627642 Timestamp [UCT]: 2024-08-02 19:40:42 Age [y:d:h:m:s]: 00:204:11:39:59
Block: 1079345 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 145990 RingCT/type: yes/0
Extra: 0134c2eb65e5bcef1608978cf4a3b428e453e452f0f7ac5e6d7a258a387b666e6b021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4f41a9315af39e4b171f2c5380a2e66bb9252680c9248bfa0eb1e0836f186045 0.600000000000 1552258 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": 1079355, "vin": [ { "gen": { "height": 1079345 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4f41a9315af39e4b171f2c5380a2e66bb9252680c9248bfa0eb1e0836f186045" } } ], "extra": [ 1, 52, 194, 235, 101, 229, 188, 239, 22, 8, 151, 140, 244, 163, 180, 40, 228, 83, 228, 82, 240, 247, 172, 94, 109, 122, 37, 138, 56, 123, 102, 110, 107, 2, 17, 0, 0, 0, 7, 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