Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1deaf41aac6d900d818f0927bb57207af260c0b97637513c1e97963a813af2b6

Tx prefix hash: 4df1a15b8294ca920f231e3739ed9cb769f5f1e8fb17b73f6ee8e5c7d4e44174
Tx public key: 054c792b618a198f74ff23c54b20a058c1ca8ab853f49665d7d6a46315a1d681
Timestamp: 1692381919 Timestamp [UCT]: 2023-08-18 18:05:19 Age [y:d:h:m:s]: 01:193:07:16:10
Block: 828765 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 399262 RingCT/type: yes/0
Extra: 01054c792b618a198f74ff23c54b20a058c1ca8ab853f49665d7d6a46315a1d6810211000000044b8f5122000000000000000000

1 output(s) for total of 1.101431787000 dcy

stealth address amount amount idx
00: 2f8d62cf39c7cadb2836c9f620e88401d4adf557ee9aacb9a647c854f89e5212 1.101431787000 1281109 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": 828775, "vin": [ { "gen": { "height": 828765 } } ], "vout": [ { "amount": 1101431787, "target": { "key": "2f8d62cf39c7cadb2836c9f620e88401d4adf557ee9aacb9a647c854f89e5212" } } ], "extra": [ 1, 5, 76, 121, 43, 97, 138, 25, 143, 116, 255, 35, 197, 75, 32, 160, 88, 193, 202, 138, 184, 83, 244, 150, 101, 215, 214, 164, 99, 21, 161, 214, 129, 2, 17, 0, 0, 0, 4, 75, 143, 81, 34, 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