Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 77734bb33c636a7ab783e8074e0995d2d598aac59f62011925b7944dd927f4ee

Tx prefix hash: acd2c5350b1f04b661b561f5ad2bfeaf2fe6dab59ffbf9b7a934f3c716a11624
Tx public key: 25e99f683ff19604a28fe22b6c8f241868c6f0284e8e485d575840b8400e8b03
Timestamp: 1734142790 Timestamp [UCT]: 2024-12-14 02:19:50 Age [y:d:h:m:s]: 00:105:10:11:31
Block: 1174712 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 75123 RingCT/type: yes/0
Extra: 0125e99f683ff19604a28fe22b6c8f241868c6f0284e8e485d575840b8400e8b03021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 19b5b629b50502a78de1bc1ccc19d74a3583eb01a4e5c991e78f2fd5fbe80e74 0.600000000000 1660899 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": 1174722, "vin": [ { "gen": { "height": 1174712 } } ], "vout": [ { "amount": 600000000, "target": { "key": "19b5b629b50502a78de1bc1ccc19d74a3583eb01a4e5c991e78f2fd5fbe80e74" } } ], "extra": [ 1, 37, 233, 159, 104, 63, 241, 150, 4, 162, 143, 226, 43, 108, 143, 36, 24, 104, 198, 240, 40, 78, 142, 72, 93, 87, 88, 64, 184, 64, 14, 139, 3, 2, 17, 0, 0, 0, 5, 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