Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 35c0b80eccd46443f30f231618c8d318f5893608c0a4bcb78557d5cef2814241

Tx prefix hash: 9ba5cba42d6b28f5f6202176d7f45aa972aa4ad8c891157179478f3d22a5a31b
Tx public key: 899bda3364482305158f7632c69a2c82af81f5c5a958db165a926d7de4f4f385
Timestamp: 1722844246 Timestamp [UCT]: 2024-08-05 07:50:46 Age [y:d:h:m:s]: 00:171:01:31:05
Block: 1081129 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 122340 RingCT/type: yes/0
Extra: 01899bda3364482305158f7632c69a2c82af81f5c5a958db165a926d7de4f4f385021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fbf96c6e892e379607d1f8ec186fffd772ad69b5929ed8977b4328bfb5f8d9d6 0.600000000000 1554754 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": 1081139, "vin": [ { "gen": { "height": 1081129 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fbf96c6e892e379607d1f8ec186fffd772ad69b5929ed8977b4328bfb5f8d9d6" } } ], "extra": [ 1, 137, 155, 218, 51, 100, 72, 35, 5, 21, 143, 118, 50, 198, 154, 44, 130, 175, 129, 245, 197, 169, 88, 219, 22, 90, 146, 109, 125, 228, 244, 243, 133, 2, 17, 0, 0, 0, 4, 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